ЦПУ в STOP при обращении к AI ET200

Промышленные Логические Контроллеры SIMATIC S7-200/300/400
Post Reply
volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Tue Apr 10, 2018 4:35 pm

Никогда не имел дело со станциями распределенного ввода-вывода. Собрал на столе минимальную конфигурацию:
1)CPU S7-315-2 PN/DP 315-2EH13-0AB0 - старая ревизия ЦПУ. Пришивку обновил до последней v.2.6.12
2)ET 200M PROFINET (IM153-4 HF)
3)AI 8*13 BIT 331-1KF01-0AB0 подключен к ЕТ.

ЕТ и ЦПУ пингуются.

После загрузки ПО в ЦПУ процессор вываливается в STOP. Только если в программе отсутствуют опросы входов AI, ЦПУ остается в RUN.

Есть ли какие-то нюансы настройки PROFINET, загрузки ПО или адрессации входов/выходов, подключенных к ЕТ? В чем проблема?
Лог диагностики ЦПУ
Show
Diagnostic buffer of module CPU 315-2 PN/DP

Order No./ Description Component Version
6ES7 315-2EH13-0AB0 Hardware 1
- - - Firmware V 2.6.12
Boot Loader Firmware expansion A 6.11.8

Rack: 0
Slot: 2


Serial number: S C-UDL863922006


Event 1 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
03:48:36.520 PM 04/10/2018
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 2 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
03:48:36.517 PM 04/10/2018
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 3 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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 by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
03:46:31.513 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B13 7713)


Event 4 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by stop switch being activated
Startup information:
- Startup with modified system configuration
- 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 by switch setting; 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 by switch setting; last power on backed up
Requested OB: Startup OB (OB100)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
03:46:31.509 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4303 0B13 7713)


Event 5 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by stop switch being activated
Startup information:
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STOP (internal)
Requested operating mode: STARTUP (warm restart)
Incoming event
03:46:31.420 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4303 0813 7713)


Event 6 of 76: Event ID 16# 4300
Power on backed up
Previous operating mode: No voltage
Requested operating mode: STOP (own initialization)
Incoming event
03:46:13.733 PM 04/10/2018
(Coding: 16# 4300 FFF3 0000 0000 0000 0000)


Event 7 of 76: Event ID 16# 494E
Power failure
Previous operating mode: STOP (internal)
Requested operating mode: No voltage
External error, Incoming event
03:46:04.708 PM 04/10/2018
(Coding: 16# 494E FF4F C000 0000 0000 0000)


Event 8 of 76: Event ID 16# 4303
STOP caused by stop switch being activated
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Incoming event
03:46:02.083 PM 04/10/2018
(Coding: 16# 4303 FF84 0000 0000 0000 0000)


Event 9 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: RUN
External error, Incoming event
03:45:46.839 PM 04/10/2018
(Coding: 16# 596D 0008 C050 07FD 0000 0001)


Event 10 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
03:13:04.086 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B14 7714)


Event 11 of 76: 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 with modified system configuration
- 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)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
03:13:04.083 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4304 0B14 7714)


Event 12 of 76: 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:
- Startup with modified system configuration
- 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 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:13:03.998 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4304 0B14 7714)


Event 13 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
03:12:53.067 PM 04/10/2018
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 14 of 76: 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:12:51.877 PM 04/10/2018
(Coding: 16# 4304 FF84 0000 0000 0000 0000)


Event 15 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
03:10:36.911 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B14 7714)


Event 16 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
03:10:36.908 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4563 0B14 7714)


Event 17 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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 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:10:36.825 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4563 0B14 7714)


Event 18 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
03:10:25.886 PM 04/10/2018
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 19 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
02:38:25.140 PM 04/10/2018
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 20 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
02:35:47.966 PM 04/10/2018
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 21 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
02:27:45.243 PM 04/10/2018
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 22 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
02:27:45.240 PM 04/10/2018
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 23 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
02:27:44.235 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B14 7714)


Event 24 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
02:27:44.232 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4563 0B14 7714)


Event 25 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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 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
02:27:44.145 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4563 0B14 7714)


Event 26 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
02:27:33.189 PM 04/10/2018
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 27 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
02:25:50.699 PM 04/10/2018
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 28 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
02:25:50.696 PM 04/10/2018
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 29 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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 by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
02:25:49.691 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B13 7713)


Event 30 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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 by switch setting; 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 by switch setting; last power on backed up
Requested OB: Startup OB (OB100)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
02:25:49.688 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4563 0B13 7713)


Event 31 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STOP (internal)
Requested operating mode: STARTUP (warm restart)
Incoming event
02:25:49.601 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4563 0813 7713)


Event 32 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
02:25:38.654 PM 04/10/2018
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 33 of 76: Event ID 16# 4300
Power on backed up
Previous operating mode: No voltage
Requested operating mode: STOP (own initialization)
Incoming event
02:25:31.910 PM 04/10/2018
(Coding: 16# 4300 FFF3 0000 0000 0000 0000)


Event 34 of 76: Event ID 16# 494E
Power failure
Previous operating mode: STOP (internal)
Requested operating mode: No voltage
External error, Incoming event
02:25:21.894 PM 04/10/2018
(Coding: 16# 494E FF4F C000 0000 0000 0000)


Event 35 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
02:16:41.145 PM 04/10/2018
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 36 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
02:16:41.142 PM 04/10/2018
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 37 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
02:12:50.138 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B14 7714)


Event 38 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
02:12:50.135 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4563 0B14 7714)


Event 39 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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 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
02:12:50.048 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4563 0B14 7714)


Event 40 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
02:11:47.503 PM 04/10/2018
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 41 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
02:11:47.500 PM 04/10/2018
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 42 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
02:11:46.496 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B14 7714)


Event 43 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
02:11:46.493 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4563 0B14 7714)


Event 44 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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 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
02:11:46.403 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4563 0B14 7714)


Event 45 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
02:11:35.479 PM 04/10/2018
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 46 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
02:10:06.167 PM 04/10/2018
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 47 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
02:10:06.164 PM 04/10/2018
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 48 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
02:10:05.159 PM 04/10/2018
(Coding: 16# 4302 FF68 C700 0000 0B14 7714)


Event 49 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
02:10:05.156 PM 04/10/2018
(Coding: 16# 1381 FE64 C772 4563 0B14 7714)


Event 50 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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 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
02:09:54.067 PM 04/10/2018
(Coding: 16# 4301 FF46 C772 4563 0B14 7714)


Event 51 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
12:11:34.027 AM 01/01/1994
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 52 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
12:11:34.024 AM 01/01/1994
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 53 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
12:11:33.020 AM 01/01/1994
(Coding: 16# 4302 FF68 C700 0000 0B14 7714)


Event 54 of 76: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
12:11:33.016 AM 01/01/1994
(Coding: 16# 1381 FE64 C772 4563 0B14 7714)


Event 55 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
STOP due to: STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Startup information:
- Startup with modified system configuration
- 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 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
12:11:21.923 AM 01/01/1994
(Coding: 16# 4301 FF46 C772 4563 0B14 7714)


Event 56 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
12:11:10.975 AM 01/01/1994
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 57 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
12:10:06.707 AM 01/01/1994
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)


Event 58 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
12:10:06.704 AM 01/01/1994
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)


Event 59 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- 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 by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
12:10:05.700 AM 01/01/1994
(Coding: 16# 4302 FF68 C700 0000 0B13 7713)


Event 60 of 76: Event ID 16# 1381
Request for manual warm restart
Startup information:
- Startup with modified system configuration
- 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 by switch setting; 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 by switch setting; last power on backed up
Requested OB: Startup OB (OB100)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
12:10:05.696 AM 01/01/1994
(Coding: 16# 1381 FE64 C772 0000 0B13 7713)


Event 61 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
Startup information:
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STOP (internal)
Requested operating mode: STARTUP (warm restart)
Incoming event
12:10:05.608 AM 01/01/1994
(Coding: 16# 4301 FF46 C772 0000 0813 7713)


Event 62 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
12:09:38.596 AM 01/01/1994
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 63 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
cause of error: Bps not suitable for PROFINET IO
operating mode: STOP (internal)
External error, Incoming event
12:08:29.010 AM 01/01/1994
(Coding: 16# 596D 0004 C050 07FD 0000 0001)


Event 64 of 76: Event ID 16# 430E
Memory reset executed
Previous operating mode: STOP (memory reset)
Requested operating mode: STOP (own initialization)
Incoming event
12:03:12.475 AM 01/01/1994
(Coding: 16# 430E FF23 0000 0000 0000 0000)


Event 65 of 76: Event ID 16# 4546
STOP caused by CPU memory management
Previous operating mode: STOP (own initialization)
Requested operating mode: STOP (memory reset)
Internal error, Incoming event
12:03:10.969 AM 01/01/1994
(Coding: 16# 4546 FF32 C0C0 8FFE 0000 0000)


Event 66 of 76: Event ID 16# 4300
Power on backed up
Previous operating mode: No voltage
Requested operating mode: STOP (own initialization)
Incoming event
12:03:10.969 AM 01/01/1994
(Coding: 16# 4300 FFF3 0000 0000 0000 0000)


Event 67 of 76: Event ID 16# 6522
Illegal module: replace module and reset memory
Operating mode: STOP (own initialization)
Internal error, Incoming event
12:03:10.969 AM 01/01/1994
(Coding: 16# 6522 FF03 0000 0001 0001 8FFE)


Event 68 of 76: Event ID 16# 4580
STOP: backup buffer contents inconsistent (no transition to RUN)
Previous operating mode: No voltage
Requested operating mode: STOP (internal)
Internal error, Incoming event
12:02:57.077 AM 01/01/1994
(Coding: 16# 4580 FFF4 0000 0002 0000 0000)


Event 69 of 76: Event ID 16# 494E
Power failure
Previous operating mode: STOP (internal)
Requested operating mode: No voltage
External error, Incoming event
12:02:57.076 AM 01/01/1994
(Coding: 16# 494E FF4F C000 0000 0000 0000)


Event 70 of 76: Event ID 16# 4303
STOP caused by stop switch being activated
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Incoming event
12:02:52.939 AM 01/01/1994
(Coding: 16# 4303 FF84 0000 0000 0000 0000)


Event 71 of 76: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Time for time stamp at the last non backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
12:02:18.956 AM 01/01/1994
(Coding: 16# 4302 FF68 C700 0000 0013 7713)


Event 72 of 76: Event ID 16# 1381
Request for manual warm restart
Startup information:
- Startup without modified system configuration
- No difference between setpoint and actual configuration
- Time for time stamp at the last non backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; 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 by switch setting; last power on backed up
Requested OB: Startup OB (OB100)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
12:02:18.952 AM 01/01/1994
(Coding: 16# 1381 FE64 C772 0000 0013 7713)


Event 73 of 76: Event ID 16# 4301
Mode transition from STOP to STARTUP
Startup information:
- Time for time stamp at the last non backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; 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 by switch setting; last power on backed up
Previous operating mode: STOP (internal)
Requested operating mode: STARTUP (warm restart)
Incoming event
12:02:18.704 AM 01/01/1994
(Coding: 16# 4301 FF46 C772 0000 0013 7713)


Event 74 of 76: Event ID 16# 430E
Memory reset executed
Previous operating mode: STOP (memory reset)
Requested operating mode: STOP (own initialization)
Incoming event
12:00:03.336 AM 01/01/1994
(Coding: 16# 430E FF23 0000 0000 0000 0000)


Event 75 of 76: Event ID 16# 4546
STOP caused by CPU memory management
Previous operating mode: STOP (own initialization)
Requested operating mode: STOP (memory reset)
Internal error, Incoming event
12:00:00.424 AM 01/01/1994
(Coding: 16# 4546 FF32 C0C0 0104 0000 0000)


Event 76 of 76: Event ID 16# 4580
STOP: backup buffer contents inconsistent (no transition to RUN)
Previous operating mode: No voltage
Requested operating mode: STOP (own initialization)
Internal error, Incoming event
12:00:00.000 AM 01/01/1994
(Coding: 16# 4580 FFF3 0000 0000 0000 0000)
Скрин диагностики
Show
Image

CoMod
Site Admin
Posts: 3969
Joined: Thu Feb 16, 2006 3:25 pm
Location: Russia
Contact:

Re: ЦПУ в STOP при обращении к AI ET200

Post by CoMod » Tue Apr 10, 2018 4:45 pm

Особенность при обращении к аналоговым портам, обычно расположенным, за пределами образа процесса с адресов 256 ...
к ним надо обращаться в программе как PIW256, а не IW256
то есть программа должна обращаться напрямую к Периферийному порту PIW256
а не к его образу IW256 в образе процесса

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Tue Apr 10, 2018 6:22 pm

CoMod wrote:Особенность при обращении к аналоговым портам, обычно расположенным, за пределами образа процесса с адресов 256 ...
к ним надо обращаться в программе как PIW256, а не IW256
то есть программа должна обращаться напрямую к Периферийному порту PIW256
а не к его образу IW256 в образе процесса
Так и обращаюсь - первый канал PIW 256. А терминатор никакой не нужен на шине, я тут подумал? Еще на ЦПУ горят индикаторы SF и BF, также и на ET (если я ничего не путаю).

CoMod
Site Admin
Posts: 3969
Joined: Thu Feb 16, 2006 3:25 pm
Location: Russia
Contact:

Re: ЦПУ в STOP при обращении к AI ET200

Post by CoMod » Tue Apr 10, 2018 7:18 pm

Event 9 of 76: Event ID 16# 596D
The existing network configuration do not correspond to the system requirements or configuration
logical address of the error-detecting module 2045
значит сама станция не инициализирована - не задан IP

и поэтому не может прочитать порт
Event 2 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
терминаторы не нужны

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Wed Apr 11, 2018 4:44 am

IP задан. Станция пингуется. Можно ли ЦПУ соединять по PN со станцией. Коммуникационный процессор не нужен? Гадаю уже.

POV_PDA
Posts: 97
Joined: Mon Apr 26, 2010 7:02 pm
Location: Н.Новгород

Re: ЦПУ в STOP при обращении к AI ET200

Post by POV_PDA » Wed Apr 11, 2018 6:48 am

Profinet имя у станции задано?

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Wed Apr 11, 2018 5:44 pm

Решено.
Несколько "телодвижений" заставили ЦПУ заработать:

1) у ЦПУ и станции ЕТ должны быть одинаковые режимы работы интерфейса Profinet. Например 100MBPs Fullduplex.
2) Должна быть настроена топология Profinet с указанием "партнеров". Важно указать какой именно порт используется для связи одного устройства с другим и только так оно работает.
3) Через 10Мбитный коммутатор не заработало, наверное т.к. моя станция поддерживает только 100MBps. Позже проверю с 100Мбитным коммутатором.

CoMod
Site Admin
Posts: 3969
Joined: Thu Feb 16, 2006 3:25 pm
Location: Russia
Contact:

Re: ЦПУ в STOP при обращении к AI ET200

Post by CoMod » Wed Apr 11, 2018 6:03 pm

volotovskyd wrote: 3) Через 10Мбитный коммутатор не заработало, наверное т.к. моя станция поддерживает только 100MBps.
Позже проверю с 100Мбитным коммутатором.
у меня на столе работает с гигабитным роутером :)

Rex2701
Posts: 370
Joined: Wed Oct 13, 2010 8:44 am
Location: Russian Federation

Re: ЦПУ в STOP при обращении к AI ET200

Post by Rex2701 » Wed Apr 11, 2018 6:32 pm

Создай и загрузи в контроллер пустую OB122
Раз
Show
Event 2 of 76: Event ID 16# 2942
I/O access error, reading
P area, word access, Access address: 256
Requested OB: I/O access error OB (OB122)
OB not found, or disabled, or cannot be started in the in the current operating mode
External error, Incoming event
03:48:36.517 PM 04/10/2018
(Coding: 16# 2942 FE7A 0020 0100 0000 0000)
а потом уже разбирайся, почему твоя FC20 не может прочитать адрес 256.
Два
Show
Event 1 of 76: Event ID 16# 4563
STOP caused by I/O access error (OB not loaded or not possible, or no FRB)
Breakpoint in user program: Cyclic interrupt OB (OB 35)
Priority class: 12
FC number: 20
Module address: 12
Previous operating mode: RUN
Requested operating mode: STOP (internal)
Internal error, Incoming event
03:48:36.520 PM 04/10/2018
(Coding: 16# 4563 FF84 8C70 0C23 0014 000C)

sania
Site Admin
Posts: 1372
Joined: Sat Aug 13, 2005 6:15 am
Contact:

Re: ЦПУ в STOP при обращении к AI ET200

Post by sania » Thu Apr 12, 2018 9:26 am

1) auto
2) удалить всю топологию
3) пофиг какой свич
как выше было замечено профинет работает по имени и надо задать имя станции, ип ей проц пропишет при стартапе

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Fri Apr 13, 2018 6:59 pm

Завтра попробую, отпишусь. У меня выдавало ошибки в диагностике что-то вроде о несовместимости с PNIO и т.п., если не ошибаюсь.

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Sat Apr 14, 2018 5:45 pm

sania wrote:1) auto
2) удалить всю топологию
3) пофиг какой свич
как выше было замечено профинет работает по имени и надо задать имя станции, ип ей проц пропишет при стартапе
Действительно, заработало и так. Не понимаю тогда, почему изначально не работало. Всем спасибо.

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Tue Jun 12, 2018 4:04 pm

И снова здравствуйте ((
Опять двадцать пять! Проблема вернулась.
ОЧЕНЬ СРОЧНО нужно решить проблему. STEP7 5.5.
Кто-нибудь срочно пошагово может описать создание следующей конфигурации: ЦПУ 315-2 PN/DP без модулей. С ним через коммутатор соединена станция ЕТ200М 153-4 PN/HF V4.0, к которой присоединен AI 8x13bit 331-1KF01-0AB0. После заливки в ЦПУ проекта процессор переходит в "СТОП" и горит "SF".
Еще вопрос: какая разница между IM153-4 PN HF V4.0 и IM153-4 PN HF V4.0 Shared Device в Hardware? И какие модули, присоединяемый к ЕТ нужно выбирать - из выпадающего списка станции IM153-4 или как обычно из списка SM-300.
И еще. У меня сохранился короткий проект, который в предыдущий раз заработал. Он и сейчас работает, но только на реальном ПЛК. При попытке залить этот проект в PLCSIM его процессор тоже переходит в STOP и горит SF. Со станциями ET PLCSIM вообще дружит?

Всем заранее спасибо за ответ.

Dfcz
Posts: 875
Joined: Tue Dec 26, 2006 5:21 am
Location: Russia

Re: ЦПУ в STOP при обращении к AI ET200

Post by Dfcz » Fri Jun 15, 2018 2:17 pm

Пошагово только спецы Сименс, если приедут.
1. Что бы легче было разбираться, проц ставь в стоп, и пока все не "загорится зелененьким" стартовать не надо.
2. В симуляторе много чего не работает.

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Sun Jun 17, 2018 7:16 pm

Вот что нашел.

""Only the CPU 315-2DP, CPU 316-2DP, and CPU 318-2 CPUs download
an I/O configuration. If you download a program from another S7-300
CPU, the system data does not include the I/O configuration. This
causes errors when you attempt to access peripheral I/O in S7-PLCSIM.
To correct this, create an CPU 315-2DP, CPU 316-2DP, or CPU 318-2
station and put a copy of your hardware configuration into it. Download
the hardware configuration from the CPU 315-2DP, CPU 316-2DP, or
CPU 318-2 to S7-PLCSIM."

Короче, для тестирования в PLCSIM создаю новую аппаратную конфигурацию с поддерживаемым и подходящим для меня функционалом ЦПУ и станцией с Profibus, тестирую на ней, потом перед заливкой в контроллер снова меняю конфигурацию на верную и заливаю. Все получилось. Вот так неожиданные костыли! Не ожидал такого от Siemens!

Всем добра.

Dfcz
Posts: 875
Joined: Tue Dec 26, 2006 5:21 am
Location: Russia

Re: ЦПУ в STOP при обращении к AI ET200

Post by Dfcz » Mon Jun 18, 2018 3:35 pm

Да нет там никаких костылей.

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Thu Apr 11, 2019 5:40 pm

Народ, выручайте! (oo)
Периодически возвращаюсь к программированию новых конфигураций со станциями ET200M 153-4 HF V4.0.
И практически каждый раз возникают траблы с работой таких конфигураций по Profinet.
Коротко о конфигурации: создал пустой проект, в hardware создал 4 стойки rack с CPU 315-2 PN/DP, IM360 (S), 3-мя IM361 (R), станцией IM153-4 HF, к которой подключен 1 модуль AI 8х13bit. Пописал IP, все пингуются, программа состоит из одного пустого ОВ1.
После заливки всего этого добра в ЦПУ горит SF на ЦПУ и моргает BF2, на станции моргает BF2.
Если подключить модуль AI к одной из стоек CPU и добавить OB86 и 122 в реальную программу, то ЦПУ в STOP не отправляется, но не видит сигналы, подключенные к станции ET, видит только сигналы AI, подключенных к CPU.
В чем подвох?! Что не так делаю? Настройти Profinet дефолтные, только IP прописываю.

Image

CoMod
Site Admin
Posts: 3969
Joined: Thu Feb 16, 2006 3:25 pm
Location: Russia
Contact:

Simatic Automation Tool

Post by CoMod » Thu Apr 11, 2019 6:01 pm

В чем подвох?! Что не так делаю?
Не смотришь в буфер диагностики - там описываются причины возникновения ошибок (boom) (h)
У Профинет устройств помимо IP-адреса ещё бывает Профинет имя.
Запусти Simatic Automation Tool и просканируй сеть
Image

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: Simatic Automation Tool

Post by volotovskyd » Thu Apr 11, 2019 6:24 pm

CoMod wrote:
Thu Apr 11, 2019 6:01 pm
В чем подвох?! Что не так делаю?
Не смотришь в буфер диагностики - там описываются причины возникновения ошибок (boom) (h)
У Профинет устройств помимо IP-адреса ещё бывает Профинет имя.
Запусти Simatic Automation Tool и просканируй сеть
Image
Имя присвоено. В диагностике станции External Error. В диагностике ЦПУ
Лог диагностики ЦПУ
Show
Diagnostic buffer of module CPU 315-2 PN/DP

Order No./ Description Component Version
6ES7 315-2EH13-0AB0 Hardware 1
- - - Firmware V 2.6.12
Boot Loader Firmware expansion A 6.11.8

Rack: 0
Slot: 2


Serial number: S C-UDL863922006


Event 1 of 10: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non 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 startup not permitted, corrections in parameter assignment, submodule, etc. necessary
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
04:14:15.716 PM 04/11/2019
(Coding: 16# 4302 FF68 C700 0000 0314 1714)


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 with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non 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 startup not permitted, corrections in parameter assignment, submodule, etc. necessary
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
04:14:15.712 PM 04/11/2019
(Coding: 16# 1381 1B64 C772 4304 0314 1714)


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:
- Startup with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non 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 startup not permitted, corrections in parameter assignment, submodule, etc. necessary
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
04:14:15.502 PM 04/11/2019
(Coding: 16# 4301 FF46 C772 4304 0314 1714)


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
04:14:02.713 PM 04/11/2019
(Coding: 16# 4304 FF84 0000 0000 0000 0000)


Event 5 of 10: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non 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 startup not permitted, corrections in parameter assignment, submodule, etc. necessary
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:19:25.527 PM 04/11/2019
(Coding: 16# 4302 FF68 C700 0000 0314 1714)


Event 6 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 with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non 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 startup not permitted, corrections in parameter assignment, submodule, etc. necessary
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:19:25.523 PM 04/11/2019
(Coding: 16# 1381 1B64 C772 4304 0314 1714)


Event 7 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:
- Startup with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non 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 startup not permitted, corrections in parameter assignment, submodule, etc. necessary
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:19:25.354 PM 04/11/2019
(Coding: 16# 4301 FF46 C772 4304 0314 1714)


Event 8 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:19:12.389 PM 04/11/2019
(Coding: 16# 4304 FF84 0000 0000 0000 0000)


Event 9 of 10: Event ID 16# 4302
Mode transition from STARTUP to RUN
Startup information:
- Startup with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of automatic startup type at power on:
- Warm restart triggered by switch setting; last power on backed up
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
03:08:51.686 PM 04/11/2019
(Coding: 16# 4302 FF68 C700 0000 0313 1713)


Event 10 of 10: Event ID 16# 1381
Request for manual warm restart
STOP due to: STOP caused by stop switch being activated
Startup information:
- Startup with modified system configuration
- Difference between setpoint and actual configuration
- Time for time stamp at the last non backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of automatic startup type at power on:
- Warm restart triggered by switch setting; last power on backed up
Requested OB: Startup OB (OB100)
Priority class: 27
Incoming event
03:08:51.682 PM 04/11/2019
(Coding: 16# 1381 1B64 C772 4303 0313 1713)

CoMod
Site Admin
Posts: 3969
Joined: Thu Feb 16, 2006 3:25 pm
Location: Russia
Contact:

Re: ЦПУ в STOP при обращении к AI ET200

Post by CoMod » Thu Apr 11, 2019 6:43 pm

я немного пролистнул тему вверх... Tue Apr 10, 2018
мы ж это уже проходили ровно год назад
сейчас сразу бросается в глаза
Difference between setpoint and actual configuration
иногда монтажники не правильно обжимают эзернет кабель
Запусти Simatic Automation Tool и покажи копию экрана как на моей картинке

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Thu Apr 11, 2019 7:00 pm

CoMod wrote:
Thu Apr 11, 2019 6:43 pm
я немного пролистнул тему вверх... Tue Apr 10, 2018
мы ж это уже проходили ровно год назад
сейчас сразу бросается в глаза
Difference between setpoint and actual configuration
иногда монтажники не правильно обжимают эзернет кабель
Запусти Simatic Automation Tool и покажи копию экрана как на моей картинке

ОК. Завтра. Только дождусь от Сименсов ссылку на скачку данной утилиты.

CoMod
Site Admin
Posts: 3969
Joined: Thu Feb 16, 2006 3:25 pm
Location: Russia
Contact:

Re: ЦПУ в STOP при обращении к AI ET200

Post by CoMod » Thu Apr 11, 2019 7:15 pm


Dfcz
Posts: 875
Joined: Tue Dec 26, 2006 5:21 am
Location: Russia

Re: ЦПУ в STOP при обращении к AI ET200

Post by Dfcz » Fri Apr 12, 2019 9:26 am

volotovskyd wrote:
Thu Apr 11, 2019 5:40 pm
….
Если подключить модуль AI к одной из стоек CPU и добавить OB86 и 122 в реальную программу, то ЦПУ в STOP не отправляется, но ….
На кой ляд добавлять ОВ86 и ОВ122? Чтобы проц в стоп не вставал? А смысл? Проблема-то не уйдет от этого.

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Fri Apr 12, 2019 7:14 pm

Не дождался от Сименса ссылку на скачивание утилиты. Но и не понадобилось. Помогло следующее - проект в ПЛК залил не с помощью опции Download, а выбрав пункт "Compile and download objects...". После блоки программы залил отдельно. Всем добра.

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Fri Apr 12, 2019 7:17 pm

Dfcz wrote:
Fri Apr 12, 2019 9:26 am
volotovskyd wrote:
Thu Apr 11, 2019 5:40 pm
….
Если подключить модуль AI к одной из стоек CPU и добавить OB86 и 122 в реальную программу, то ЦПУ в STOP не отправляется, но ….
На кой ляд добавлять ОВ86 и ОВ122? Чтобы проц в стоп не вставал? А смысл? Проблема-то не уйдет от этого.
...но помогает понять какая часть проекта не работает. В моем случае стало очевидным, что все адреса станции ЕТ недоступны (в SCADA это сразу стало очевидно).

volotovskyd
Posts: 79
Joined: Mon Aug 13, 2012 2:23 pm

Re: ЦПУ в STOP при обращении к AI ET200

Post by volotovskyd » Sat Apr 13, 2019 5:46 pm

CoMod wrote:
Thu Apr 11, 2019 7:15 pm
тут видел
https://yadi.sk/d/FRabwCLYBIshtw
Спасибо! Буду пользовать. На форуме есть рейтинги и способы отблагодарить соответствующим образом?

Post Reply