Area length error when reading step7 - Исправление ошибок и поиск оптимальных решений проблем

Old
November 21st, 2009, 05:01 AM

Member

India

Join Date: Oct 2004

Location: India.

Posts: 750

Area length error when reading

Hi there
Iam unable to understand as to why PLC gives «

Area Length error when reading

» if I add «

A#call_fwd_I

» at the very end of the block.

Code:

FUNCTION_BLOCK FB 100
TITLE =
//1)check if station is enabled.
//2)if enabled then wait for the demand of that station.
//3)iF demand of all the active stations comes then generate the sequence 
//number orderly.
VERSION : 0.1


VAR_INPUT
  stn1_ena_hmi : BOOL ;    
  stn2_ena_hmi : BOOL ;    
  stn3_ena_hmi : BOOL ;    
  stn4_ena_hmi : BOOL ;    
END_VAR
VAR_IN_OUT
  stn4_call_I : BOOL ;    
  stn3_call_I : BOOL ;    
  stn2_call_I : BOOL ;    
  stn1_call_I : BOOL ;    
  call_fwd_I : BOOL ;    
END_VAR
VAR
  stn1_active : BOOL ;    
  stn2_active : BOOL ;    
  stn3_Active : BOOL ;    
  stn4_active : BOOL ;    
  call_fwd : BOOL ;    
  fp_st1 : BOOL ;    
  fp_st2 : BOOL ;    
  fp_st3 : BOOL ;    
  fp_st4 : BOOL ;    
  ena_inc : INT ;    
  fn_st1 : BOOL ;    
  fn_st2 : BOOL ;    
  fn_st3 : BOOL ;    
  fn_st4 : BOOL ;    
  fwd_demand : INT ;    
  fp_st1_f : BOOL ;    
  fp_st2_f : BOOL ;    
  fp_st3_f : BOOL ;    
  fp_st4_f : BOOL ;    
  fn_st1_f : BOOL ;    
  fn_st2_f : BOOL ;    
  fn_st3_f : BOOL ;    
  fn_st4_f : BOOL ;    
  stn4 : INT ;    
  stn3 : INT ;    
  stn2 : INT ;    
  stn1 : INT ;    
  fp_reset : BOOL ;    
END_VAR
VAR_TEMP
  count : INT ;    
  count1 : INT ;    
END_VAR
BEGIN
NETWORK
TITLE =to know number of the active stuffing station

//increment the counter

      A     #stn1_ena_hmi; 
      FP    #fp_st1; 
      JCN   st2; 
      L     #ena_inc; 
      L     1; 
      +I    ; 
      T     #ena_inc; 



st2:  A     #stn2_ena_hmi; 
      FP    #fp_st2; 
      JCN   st3; 
      L     #ena_inc; 
      L     1; 
      +I    ; 
      T     #ena_inc; 

st3:  A     #stn3_ena_hmi; 
      FP    #fp_st3; 
      JCN   st4; 
      L     #ena_inc; 
      L     1; 
      +I    ; 
      T     #ena_inc; 

st4:  A     #stn4_ena_hmi; 
      FP    #fp_st4; 
      JCN   end1; 
      L     #ena_inc; 
      L     1; 
      +I    ; 
      T     #ena_inc; 

end1: NOP   0; 

//decrement the counter


      A     #stn1_ena_hmi; 
      FN    #fn_st1; 
      JCN   st2n; 
      L     #ena_inc; 
      L     -1; 
      +I    ; 
      T     #ena_inc; 

st2n: A     #stn2_ena_hmi; 
      FN    #fn_st2; 
      JCN   st3n; 
      L     #ena_inc; 
      L     -1; 
      +I    ; 
      T     #ena_inc; 

st3n: A     #stn3_ena_hmi; 
      FN    #fn_st3; 
      JCN   st4n; 
      L     #ena_inc; 
      L     -1; 
      +I    ; 
      T     #ena_inc; 


st4n: A     #stn4_ena_hmi; 
      FN    #fn_st4; 
      JCN   end2; 
      L     #ena_inc; 
      L     -1; 
      +I    ; 
      T     #ena_inc; 
end2: NOP   0; 




NETWORK
TITLE =to know number of the call forward demands

//increment the counter
      A     #stn4_ena_hmi; 
      A     #stn4_call_I; 
      FP    #fp_st1_f; 
      JCN   st2f; 
      L     #fwd_demand; 
      L     1; 
      +I    ; 
      T     #fwd_demand; 

st2f: A     #stn3_call_I; 
      A     #stn3_ena_hmi; 
      FP    #fp_st2_f; 
      JCN   st3f; 
      L     #fwd_demand; 
      L     1; 
      +I    ; 
      T     #fwd_demand; 

st3f: A     #stn2_call_I; 
      A     #stn2_ena_hmi; 
      FP    #fp_st3_f; 
      JCN   st4f; 
      L     #fwd_demand; 
      L     1; 
      +I    ; 
      T     #fwd_demand; 

st4f: A     #stn1_call_I; 
      A     #stn1_ena_hmi; 
      FP    #fp_st4_f; 
      JCN   end3; 
      L     #fwd_demand; 
      L     1; 
      +I    ; 
      T     #fwd_demand; 

end3: NOP   0; 

//decrement the counter


      A     #stn4_call_I; 
      A     #stn4_ena_hmi; 
      FN    #fn_st1_f; 
      JCN   st2r; 
      L     #fwd_demand; 
      L     -1; 
      +I    ; 
      T     #fwd_demand; 

st2r: A     #stn3_call_I; 
      A     #stn3_ena_hmi; 
      FN    #fn_st2_f; 
      JCN   st3r; 
      L     #fwd_demand; 
      L     -1; 
      +I    ; 
      T     #fwd_demand; 

st3r: A     #stn2_call_I; 
      A     #stn2_ena_hmi; 
      FN    #fn_st3_f; 
      JCN   st4r; 
      L     #fwd_demand; 
      L     -1; 
      +I    ; 
      T     #fwd_demand; 


st4r: A     #stn1_call_I; 
      A     #stn1_ena_hmi; 
      FN    #fn_st4_f; 
      JCN   end4; 
      L     #fwd_demand; 
      L     -1; 
      +I    ; 
      T     #fwd_demand; 

end4: NOP   0; 









NETWORK
TITLE =
//to check is number of active stations are equal to call fwd demand
      O(    ; 
      L     #fwd_demand; 
      L     0; 
      ==I   ; 
      )     ; 
      O     #call_fwd; 
      JC    end5; 
      L     #fwd_demand; 
      L     #ena_inc; 
      ==I   ; 
      JCN   end5; 

      S     #call_fwd_I; 
end5: NOP   0; 
////reset the set bit after the acknowledgement is received

      A     #call_fwd_I; 
      FN    #fp_reset; 
      JCN   end6; 
      R     #call_fwd; 
      R     #stn1_call_I; 
      R     #stn2_call_I; 
      R     #stn3_call_I; 
      R     #stn4_call_I; 

      L     0; 
      T     #stn4; 
      T     #stn3; 
      T     #stn2; 
      T     #stn1; 
end6: NOP   0; 


NETWORK
TITLE =
//once the call_fwd is set now name the stations according to priority basis

      A     #call_fwd_I; 
      AN    #call_fwd; 
      JCN   fin; 

      SET   ; 
      S     #call_fwd; 


      LAR1  P##stn4_call_I; 
      LAR2  P##stn4; 
      L     5; 
      T     #count1; 

      L     4; 
c2:   T     #count; 
      A      [AR1,P#0.0]; 
      JCN   c1; 
      L     #count1; 
      L     #count; 
      -I    ; 
      T     W [AR2,P#0.0]; 
      JU    c3; 

c1:   L     #count1; 
      L     -1; 
      +I    ; 
      T     #count1; 



c3:   +AR1  P#0.1; 
      +AR2  P#2.0; 

      L     #count; 
      LOOP  c2; 


fin:  NOP   0; 


      A     #call_fwd_I; 
END_FUNCTION_BLOCK

What on?

regards

__________________
Manmeet

November 21st, 2009, 05:51 AM	#2
Lifetime Supporting Member Join Date: Jan 2005 Location: Down South Posts: 2,711	From Siemens web site Description: The area length error appears if references are made to addresses that do not exist in the STEP 7 program or when parameterizing the block call. The Online Help in STEP 7 gives two reasons for this: The value addressed by the access address is outside or not entirely inside the permissible address area (CPU-specific size). Due to an incorrect address calculation the addressed value is >65535. In the case of indirect addressing, an address value of greater than 65535 might occur through incorrect calculation. This value can no longer be entered correctly in the detail information of the event. Then for S7-300 a 0 is entered and displayed as access address and the calculated value modulo 65535 for S7-400. __________________ Regards Dave «When you are courting a nice girl an hour seems like a second. When you sit on a red-hot cinder a second seems like an hour. That’s relativity.» Albert Einstein (1879-1955)

November 21st, 2009, 06:20 AM	#3
Member Join Date: Sep 2005 Location: UK Posts: 879	May have something to do with using AR2 to store your pointer offsets when AR2 points to the Instance DB when using FB’s. Set some breakpoints and step through your code keeping an eye on the DB,AR registers. Last edited by STL???; November 21st, 2009 at 06:24 AM.

November 21st, 2009, 06:47 AM	#4
Member Join Date: Oct 2004 Location: India. Posts: 750	Hi 504bloke i have used #call_fwd_I as in_out variable, so even if I use M0.0 for it, it give me error.So no problem with outside the access area. Incorrect calculation cannot apprehend why. But some thing to do with AR2 as STL?? said. Because when I write LAR2 P##call_fwd_I A #call_fwd_I Problem disappears!! Also problem only comes when logic in network 4 gets executed. Some more light…………….. __________________ Manmeet

November 21st, 2009, 06:56 AM	#5
Lifetime Supporting Member Join Date: Nov 2006 Location: UK Posts: 6,468	Stop, Go directly to jail, if you pass Go, do not collect �200

November 21st, 2009, 07:13 AM	#6
Lifetime Supporting Member Join Date: Nov 2006 Location: UK Posts: 6,468	.. I’ve just been searching for a relevant post but to no avail. ALL FB interface variables (IN/IN_OUT/OUT/STAT) are accessed using the instance DB and AR2. If you modify AR2 inside an FB you cannot access an interface variable whilst AR2 is being used for something. You must save AR2 in the temp area, Do your processing using AR2 (only using temps). Restore AR2 from the temp area. All interface variable access is now allowed.

Old
November 21st, 2009, 07:43 AM

Member

India

Join Date: Oct 2004

Location: India.

Posts: 750

Always restore AR2 inside FB after using it !!

Ah L D[AR2,P#0.0] great
Am feeling relived now…

1) I declared a variable in TEMP Area (TEMP0) with data type DW.
2) Before using AR2 in network 4 i wrote «TAR2 #TEMP0»
3) After using AR2 i restored it by «LAR2 #TEMP0»

Now PLC has no problem !!

Just Point AR2 to any interface variable declared inside IN/OUT/IN_OUT/STAT (

THIS IS WRONG)

Lesson:

Always restore AR2 inside FB after using it !! else if you access an interface variable you will have RED LIGHT.

Thanks and Cheers !

__________________
Manmeet

Last edited by manmeetvirdi; November 21st, 2009 at 08:11 AM.

November 21st, 2009, 07:48 AM	#8
Lifetime Supporting Member Join Date: Nov 2006 Location: UK Posts: 6,468	You were lucky to get an area read error and a red light — this is not always the case. Let say that you have two ints in the stat area (iFred then iBert). AR2 gets incremented by 2 bytes L iFred is actually loading iBert…. the possibilities for confusion are endless.

November 21st, 2009, 08:18 AM	#9
Member Join Date: Oct 2004 Location: India. Posts: 750	Ok LD I got the point. Just pointing AR2 to any interface variable declared inside IN/OUT/IN_OUT/STAT (it will remove RED light though) and then performing actions like «L #iFred» will load some value which is not present in #iFred. Great point ! In my code itself if I just add LAR2 P##stn1_active L #stn4 A #call_fwd_I accumulator does not show the right value in #stn4 even though RED LIGHT is gone !! Thats Mind blowing !!!! LD you can make a puzzle based on this __________________ Manmeet Last edited by manmeetvirdi; November 21st, 2009 at 08:21 AM.

Источник

Hi I’m a bit new to Siemens, we;re an Allen Bradley plant…until now. we just got a brand new used press and it has a seimens controller on it. The press doesn’t seem to have any manual functions so I as asked to move the cylinder, but I can’t until I clear this fault. it won’t do anything.

I’m told I’m working with an older processor, s7 300?I don’t really know seimens that well.

I saved the diagnostics buffer as a text file and pasted it below. in case that helps solve my problem. I’m thinking it’s just having trouble communicating with remote IO, but I’m not sure. I might be trying to communicate to a robot that used to be there that no longer is.

Diagnostic buffer of module CPU 314C-2 DP

Order No./ Description     Component    Version
6ES7 314-6CH04-0AB0    Hardware     5
— — —    Firmware     V 3.3.11
Boot Loader    Firmware expansion     A 37.12.12

Rack: 0
Slot: 2

Serial number: S Q-EDU050142014

Event 1 of 10: Event ID 16# 2522
Area length error when reading
Global DB, word access, Access address: 262
Requested OB: Programming error OB (OB121)
Priority class: 1
Internal error, Incoming event
10:36:07.052 AM 04/17/2019
(Coding: 16# 2522 0179 0024 0106 0000 0000)

Event 2 of 10: Event ID 16# 2522
Area length error when reading
Global DB, word access, Access address: 260
Requested OB: Programming error OB (OB121)
Priority class: 1
Internal error, Incoming event
10:36:07.052 AM 04/17/2019
(Coding: 16# 2522 0179 0024 0104 0000 0000)

Event 3 of 10: Event ID 16# 2943
I/O access error, writing
P area, word access, Access address: 40
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
10:36:07.052 AM 04/17/2019
(Coding: 16# 2943 017A 0020 0028 0000 0000)

Event 4 of 10: Event ID 16# 2943
I/O access error, writing
P area, word access, Access address: 36
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
10:36:07.052 AM 04/17/2019
(Coding: 16# 2943 017A 0020 0024 0000 0000)

Event 5 of 10: Event ID 16# 2943
I/O access error, writing
P area, word access, Access address: 38
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
10:36:07.051 AM 04/17/2019
(Coding: 16# 2943 017A 0020 0026 0000 0000)

Event 6 of 10: Event ID 16# 2522
Area length error when reading
Global DB, word access, Access address: 262
Requested OB: Programming error OB (OB121)
Priority class: 1
Internal error, Incoming event
10:36:07.051 AM 04/17/2019
(Coding: 16# 2522 0179 0024 0106 0000 0000)

Event 7 of 10: Event ID 16# 2522
Area length error when reading
Global DB, word access, Access address: 260
Requested OB: Programming error OB (OB121)
Priority class: 1
Internal error, Incoming event
10:36:07.050 AM 04/17/2019
(Coding: 16# 2522 0179 0024 0104 0000 0000)

Event 8 of 10: Event ID 16# 2943
I/O access error, writing
P area, word access, Access address: 40
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
10:36:07.050 AM 04/17/2019
(Coding: 16# 2943 017A 0020 0028 0000 0000)

Event 9 of 10: Event ID 16# 2943
I/O access error, writing
P area, word access, Access address: 36
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
10:36:07.050 AM 04/17/2019
(Coding: 16# 2943 017A 0020 0024 0000 0000)

Event 10 of 10: Event ID 16# 2943
I/O access error, writing
P area, word access, Access address: 38
Requested OB: I/O access error OB (OB122)
Priority class: 1
External error, Incoming event
10:36:07.050 AM 04/17/2019
(Coding: 16# 2943 017A 0020 0026 0000 0000)

Источник

Hello fellow programmers!

I’ve come to you with a new problem… currently I am working on a project involving a network of 8 Siemens PLCs (ET200S IM151-8 PN/DP CPU). They all pretty much do the same thing, so they’re configured almost the same, except the HW. They all seem to work flawlessly, except one. This one, when I start it up, immediately turns on the RED SF LED. I’ve attached the Diagnostic Buffer read with Module Information inside Siemens.

I’ve also read Area length error when reading and Please help me: Area length error when reading but I couldn’t figure out what’s the solution to my problem.

I also mention that the CPU doesn’t go into STOP because I loaded all the necessary OBs in order to prevent that (learned this one from this forum ), but the boss see’s every RED thingy as a problem , so I must solve this one in order to get him off my back.

Has anyone ever dealt with this situation? Could anyone help me solve this?

Thanks in advance!
Voicu

P.S. Oh, I forgot to mention… I’m the boss…

Источник

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Request: пример с стандартным ПИД-регулятором

Кинте ссылку на пример с стандартным ПИД-регулятором, плз)
Искал, и на форуме толком нет ничего, а некоторые ссылки вообще не работают ((

Oldman: Posts: 797; Joined: Tue Aug 21, 2007 7:05 am

Re: Request: пример с стандартным ПИД-регулятором

Post

by Oldman » Thu Jul 07, 2011 7:19 pm

viewtopic.php?f=9&t=10321 , viewtopic.php?f=9&t=11293 , viewtopic.php?f=9&t=8169

это тока в этой ветке.если искать в других по ветках на английском еще можно найти тока надо захотеть.
а так проще всего не упираясь написать и сидеть ждать -пусть другие ищут.
тех кто пишет тебе после моих ответов и не находящих ничего пересылай мне .ткну носом ленивый народец.опять же есть сайт и ссылки с примерами он там смотрел ли думаю нет.

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Re: Request: пример с стандартным ПИД-регулятором

Post

by a_gricaj » Fri Jul 08, 2011 11:51 am

Эти все ссылки находил и раньше, но там теория, а мну интересует стандартный пид регулятор — там масса параметров, многие понятны так как с теорией регулирования знаком. Интерисует минимальный набор параметров которые нужны для работы регулятора. Понял, что блок регулятора надо вызывать в ОВ85 напр. или в друм в зависимости от необходимомого периода опроса — а дальше??

Какую входную величину лучше подавать — реал или в формате переферии и т.д.

Oldman: Posts: 797; Joined: Tue Aug 21, 2007 7:05 am

Re: Request: пример с стандартным ПИД-регулятором

Post

by Oldman » Fri Jul 08, 2011 12:08 pm

там на одной из ссылок есть линк на сайт komatic http://www.plc4good.org.ua/view_post.php?id=97 (это как пример).если поизучаешь сайт то и пример найдешь.ну и последнее пробуй сам писать и пытайся настраивать ПИД .ну все же есть на сайте достаточно включить мозги и напрячься.сходи на форум официальный сименса там при прочтении постов многому можно научится.есть еще такой сайт http://s7-facility.blogspot.com/ на нем тоже можно подчерпнуть много всего.ну ленишься же.скажи что я не прав.меня еще и поимели админы.кто хочет развиваться найдет способ.другое дело если б было видно что делал усилия и ничего не получается а так лень твоя виновата.звиняйте если слишком резко но на правду не обижаются.

CHANt: Posts: 501; Joined: Tue Jun 27, 2006 5:52 am; Location: Russia

Re: Request: пример с стандартным ПИД-регулятором

Post

by CHANt » Sat Jul 09, 2011 7:03 pm

a_gricaj wrote:Интересует минимальный набор параметров которые нужны для работы регулятора. Понял, что блок регулятора надо вызывать в ОВ85 напр. или в друм в зависимости от необходимомого периода опроса — а дальше??

Какую входную величину лучше подавать — реал или в формате переферии и т.д.

1) Регулятор надо вызывать в двух организационных блоках:
а) в ОВ100 вызвать со своим экземплярным блоком данных, можно не задавать входы/выходы только параметр «COM_RST» установить в единичку. Это нужно чтобы сбросить промежуточные расчеты в DB, после запуска ЦПУ, чтобы регулятор начал работать с начальными параметрами.
б) в ОВ35, которому можно задать время периодичности вызова в HWConfig, в настройках ЦПУ, в ОВ35 и выполняется конфигурирование всех входов/выходов.
2) Минимальные данные? А какой регулятор ты выбрал для работы? В общем случае:
Входа:
а) «COM_RST» в ноль
б) «MAN_ON» включить ручной режим управления
в) «MAN» задать величину открытия/закрытия в ручном режиме управления
г)»CYCLE» период расчет данных в функциональном блоке
д)»CYCLE_P» период вызова FB, обычно равный вызову ОВ35
е) «SP_INT» величина уставки
ж)»PV_IN» или «PV_PER»,тут уж выбирай как удобней. Я обычно конвертирую в контроллере все датчики сразу и работаю REALовской величиной, соответственно вход «PV_IN»
Далее, я не знаю какой тип регулятора у тебя
Выхода:
«LMN» либо «LMN_PER» опять же дело вкуса. Для «LMN» реаловскую величину нужно будет конвертнуть через FC106
Обычно вся сименсовская документация по ПИДам подкреплена примерами с моделью, т.е. можно «вживую» погонять на симуляторе. В доке написано, как называется пример, обычно он ставится вместе со Step7.

P.S. «Старый», хорош бурдеть! В отпуск надо иногда ходить!

Oldman: Posts: 797; Joined: Tue Aug 21, 2007 7:05 am

Re: Request: пример с стандартным ПИД-регулятором

Post

by Oldman » Sun Jul 10, 2011 5:15 am

все что CHANT объяснил, есть тут с примерами http://old.automation-drives.ru/as/prod … %CE&l3=doc надо тока сделать над собой усилие ну или захотеть в чем либо разобраться.сименс наверное одна из лучших контор, если не самая лучшая по техподдержке.официальных доков по базовым вещам море в том числе на русском .читай не хочу.смотреть тут страничку что привел надо Internet Explorer а не другими модными браузерами.
P.S.за советы спасибо

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Re: Request: пример с стандартным ПИД-регулятором

Post

by a_gricaj » Mon Jul 11, 2011 1:02 pm

Спасибо Вам CHANt за помощь — всегда помогаете.

Но пока не получается:
Создал я в контроллере FB41-CONT_C (ПИД регулятор) и его экземплярный блок DB41, есть также ОВ1, ОВ35, ОВ86, ОВ88, ОВ100, ОВ120 и ОВ121
В ОВ1 вставляю FB41 (без задания параметров) — заливаю в контроллер ошибки нет, открываю ОВ35 и прописываю вызов FB41 на STL:

И появляется вот такая ошибка в диагностическом буфере:

Order No./ Description Component Version
6ES7 416-2XK04-0AB0 Hardware 2
— — — Firmware V 4.0.3
Rack: 0
Slot: 3
Serial number: SVPT3373834

Event 1 of 110: Event ID 16# 2523
Area length error when writing
Instance DB, word access, Access address: 76
FB number: 41
Module address: 1412
Requested OB: Programming error OB (OB121)
Priority class: 12
Internal error, Incoming event
01:44:52.001 AM 01/01/1994

Event 2 of 110: Event ID 16# 2523
Area length error when writing
Instance DB, double-word access Access address: 72
FB number: 41
Module address: 1350
Requested OB: Programming error OB (OB121)
Priority class: 12
Internal error, Incoming event
01:44:52.001 AM 01/01/1994

Event 3 of 110: Event ID 16# 2522
Area length error when reading
Instance DB, double-word access Access address: 60
FB number: 41
Module address: 1340
Requested OB: Programming error OB (OB121)
Priority class: 12
Internal error, Incoming event
01:44:52.001 AM 01/01/1994

Event 4 of 110: Event ID 16# 2522
Area length error when reading
Instance DB, double-word access Access address: 56
FB number: 41
Module address: 1334
Requested OB: Programming error OB (OB121)
Priority class: 12
Internal error, Incoming event
01:44:52.001 AM 01/01/1994

Что я неправильно делаю??????

CHANt: Posts: 501; Joined: Tue Jun 27, 2006 5:52 am; Location: Russia

Re: Request: пример с стандартным ПИД-регулятором

Post

by CHANt » Mon Jul 11, 2011 5:02 pm

Не толкай регулятор в ОВ1! На то он и ОВ1 что у него самый низкий приоритет. Т.е. ОВ1 приостанавливает выполнение, когда другие ОВ вызываются. На это в документации на любой регулятор и указывают. Либо тогда специальные меры принимай, чтобы Cycle_P содержал реальные данные о времени выполнения ОВ1. Лучше вставь в ОВ35.

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Re: Request: пример с стандартным ПИД-регулятором

Post

by a_gricaj » Mon Jul 11, 2011 5:08 pm

Все работает (регулирование частоты привода через частотник и аналоговый датчик уровня) но есть програмная ошибка (горит INTF)
и ошибка похожая на ту, что раньше была.

То-есть лучше регулятор с параметрами запихнуть в функцию или в ОВ35 вставить???

А в библиотечном FB41 нет параметра Cycle_P. как тут поступать?

Запихнул регулятор в функцию — ошибка осталась(По аналогии из прогой которая работает у меня на заводе- хочу разобраться), где я могу быть не прав???

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

Re: Request: пример с стандартным ПИД-регулятором

Post

by sania » Mon Jul 11, 2011 5:52 pm

ааа ,сори,увидел что раньше выдал буфер
тогда сделай так:
сотри дб из списка блоков
открой там где вызываешь пид
сотри вызов дб
впиши снова
подтверди его создание
сохрани
загрузи в плк дб

a_gricaj wrote:По аналогии из прогой которая работает у меня на заводе- хочу разобраться

только если сама функция вызывается из об35,тогда будет работать правильно
вот пример

CHANt: Posts: 501; Joined: Tue Jun 27, 2006 5:52 am; Location: Russia

Re: Request: пример с стандартным ПИД-регулятором

Post

by CHANt » Mon Jul 11, 2011 6:11 pm

Не знаю, почему у тебя ЦПУ ругается на экземплярный блок данных, может что-то с ним делал? Попробуй удалить и создать снова. (Собственно, Sania уже подсказал)
Pid_fb41.zip — сконфигурировал, грузится в симулятор без проблем. Можешь посмотреть — включил П+И+Д, сконфигурировал ручное управления, задал уставку, задал датчик, определил в каком диапазоне будет лежать выход регулятора (0..100%), задал цикл расчета. в ОВ100 тоже показал как сбрасываются статические переменные.

dmitry_79: Posts: 149; Joined: Sun Dec 20, 2009 1:30 pm; Location: Russia

Re: Request: пример с стандартным ПИД-регулятором

Post

by dmitry_79 » Tue Jul 12, 2011 4:56 am

А про построение каскадных регуляторов на базе FB41 есть какая нибудь информация? Примеры? Все что сумел найти в документации — это краткое упоминание о возможности построения сложных регуляторов… ничего конкретного…

Best regards!

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Re: Request: пример с стандартным ПИД-регулятором

Post

by a_gricaj » Tue Jul 12, 2011 1:22 pm

Пока не получается — все равно висит эта програмная ошибка

Может у кого будет время, посмотрите плз мою програму (ткните носом — где я партачу), ссылка — http://webfile.ru/5434809
а пока попробую пример от CHANt

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

Re: Request: пример с стандартным ПИД-регулятором

Post

by sania » Tue Jul 12, 2011 7:13 pm

блин так зачем его 2 раза вызывать? в об1 и об35,дак ещё и без DI!
вызов фс1 перенеси в об35,а то что там сотри

P.S.возьми-ка ты лучше проект CHANt`a и не парь мозги
P.S.S. конструкция UC FB 41 подразумевает что перед ней ты задал ВСЕ необходимые ей данные
т.е. перед этим должно быть как минимум OPN DI 41

CHANt: Posts: 501; Joined: Tue Jun 27, 2006 5:52 am; Location: Russia

Re: Request: пример с стандартным ПИД-регулятором

Post

by CHANt » Tue Jul 12, 2011 7:57 pm

Можно еще добавить:
1) Зачем открывать DB41 (это экземплярный DB) командой «OPN»? Не надо. Открываются DB в теле какой нибудь функции, чтобы работать с прямой адресацией, типа: DBW2. Если его не открывать, то вид адресации будет: DB41.DBW2. А ты открыл DB и тут же обращаешься к ней по полной адресации (это я про ОВ1, раздел с частотником).
2) Отключи Д составляющую. Для уровня она тебе не нужна. Ты ее физический смысл понимаешь?
3) переключение на ручной режим (MAN_ON) и задание уровня открытия (MAN) вытащи на панель. Будет удобно тестировать регулятор и если надо отключать.
4) Обрати внимание на значения границ выхода LMN, это параметры LMN_HLM=100.0 и LMN_LLM=0.0. Если их сделать соответственно LMN_HLM=85.0 и LMN_LLM=5.0 ТО регулятор на выходе даст не более 85 условных единиц и не менее 5 условных единиц. Удобно очень оставлять некий пропуск по нижнему порогу (с точки зрения ТБ), так как регулятор не является отсекающим устройством. Или например, у тебя управляющий сигнал не 0..10В, а 2..10В.
5) LMN… Вообще есть стандартная FC106, аналогичная FC105 тобой использованная. Но, если у тебя управляющий сигнал в полном диапазоне: 0..10В, 4..20мА, 0..20мА, то тут лучше применить наверное LMN_PER, так как выход у тебя с контроллера идет. Т.е. сразу PQW518 задать.
В общем, не забывай ткнуть в FB41 мышкой и нажать F1

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Re: Request: пример с стандартным ПИД-регулятором

Post

by a_gricaj » Wed Jul 13, 2011 4:01 pm

Все получилось (сделал как советовал sania) — когда стал вызывать FC1 (а в FC1 вызываеться блок регулятора) в ОВ35 — ошибка пропала

1. Я вызывал регулятор и в ОВ35 и в FC1 — так получается нельзя? Почему??

2. Но есть работоспособный вариант когда в ОВ35 вызываеться функциональный блок регулятора строкой: UC FB41(ПИД-регулятор), и тогда больше нигде не надо вставлять FB41, а параметрирование FB41 в таком случае следует делать через его экземплярный блок??????

CHANt: Posts: 501; Joined: Tue Jun 27, 2006 5:52 am; Location: Russia

Re: Request: пример с стандартным ПИД-регулятором

Post

by CHANt » Wed Jul 13, 2011 4:21 pm

a_gricaj wrote:1. Я вызывал регулятор и в ОВ35 и в FC1 — так получается нельзя? Почему??

А как ты себе представляешь работу одного и того же два раза? В расчетах мешанина будет, результат не предсказуем…

a_gricaj wrote:2. Но есть работоспособный вариант когда в ОВ35 вызываеться функциональный блок регулятора строкой: UC FB41(ПИД-регулятор), и тогда больше нигде не надо вставлять FB41,

Второй раз только в ОВ100 надо вызывать его, для сброса stat-переменных DB41 при старте контроллера.

a_gricaj wrote:а параметрирование FB41 в таком случае следует делать через его экземплярный блок??????

Да.
А какую цель ты преследуешь вызовом UC? Левой ногой, правое ухо?

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Re: Request: пример с стандартным ПИД-регулятором

Post

by a_gricaj » Wed Jul 13, 2011 4:32 pm

Понял БОЛЬШОЕ СПС за разяснения)

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

Re: Request: пример с стандартным ПИД-регулятором

Post

by sania » Wed Jul 13, 2011 6:43 pm

ошибка пропала не от переноса фс,а от удаления UC
в оригинальной проге скорей всего перед UC задан DI

а вообще прикольно, в 400-м при 5 строчках кода, скан об1 должен быть 1-2 мсек,а в настройках пид — 100.
т.е. его ошибка в 50 раз
если это тебя удовлетворяет…он же работает как он/офф,может задуматься о том что пид и не нужен?

a_gricaj: Posts: 202; Joined: Wed Mar 19, 2008 1:12 pm; Location: Ukraine

Re: Request: пример с стандартным ПИД-регулятором

Post

by a_gricaj » Thu Jul 14, 2011 3:08 pm

А, что ты меешь ввиду под «ДИ»??????????????????????

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

Re: Request: пример с стандартным ПИД-регулятором

Post

by sania » Thu Jul 14, 2011 4:17 pm

извиняюсь,лень было переходить с языка на язык
DI : инстанс дата блок.
вызов : CALL FB41, DB41 ,подразумевает : вызвать FB41 с DI41

Источник

Siemens Step7 Error codes and causes, find the error number in table and check cause.

Error number:	Text:	Cause:	Remedy:
1:2063	TBI error 2063 Error during the function chdir	TBI can occur with the call AUTgetlinkedObjects. There should be an AUT API tracer in the meantime.
7:6160	CPUs can only be connected via K bus or MPI bus (line 1)		Split the desired path of the global data into several circuits. Make sure that you only use on bus per circuit.
11:103	Cannot read CPU information on module, such as rated type, actual type and status of the module. Module might not be configured.		Check the logical address of the module. Check the slot and the configured slot.
13:31		The online connection from the PG to the module (SDB addressee) could not be set up. Connection hardware is faulty (e.g. connection cable removed).	Clear the fault in the connection to the module (SDB addressee) and you can then repeat the attempt to set up the connection in this dialog.
		The online connection from the PG to the module (SDB addressee) could not be set up. The module (SDB addressee) is in the wrong operating mode.	Change the operating mode of the module (SDB addressee) and you can then repeat the attempt to set up the connection in this dialog.
		The online connection from the PG to the module (SDB addressee) could not be set up. You have specified an incorrect MPI address with STEP 7.	If you have specified an incorrect MPI address, then: 1. Acknowledge this dialog 2. Correct the MPI address with STEP 7 3. Restart the “Load” function
13:32	There is a problem with the connection to the receiver of the HW configuration	The online connection from the PG to the module (SDB addressee) could not be set up. The module recognized an error with the next communications call.	Clear the fault in the connection, change the operating mode of the module or clear the storage bottleneck on the module and then you can repeat the attempt to set up the connection in this dialog.
		Connection hardware is faulty (e.g. connection cable removed)	Plug the cable in.
		Module is in the wrong operating mode	Check the operating mode.
		Storage bottleneck on the module
		Inconsistent HW configuration in the PG	If the HW configuration is inconsistent in the PG, then: 1. Acknowledge this dialog 2. Correct the HW configuration in the configuration table 3. Restart the “Load” function
		When loading the system data on to the memory card, this message is displayed if there are invalid SDBs in the SDB folder.	Delete the system data in the SIMATIC Manager and then restart the HW Config.
13:48	Internal error 0400 Station cannot be generated.	The station cannot be created in the selected project because …
		The project directory is write-protected	Remove the write-protection for the project directory
		The project directory is on a network drive and the connection cannot be set up	Set up the connection to the network drive
		No more storage capacity on the target drive	Delete any data no longer needed on the target drive

Error number:	Text:	Cause:	Remedy:
13:76	Inconsistent hardware configuration in the programming device.	Inconsistent HW configuration in the PG	In HW Config analyze the HW configuration via the menu “StationCheck consistency”.
		Folder “…SIEMENSSTEP7S7TMP” is missing or write-protected
		Missing authorization or an options package that generates the SDBs for a specific module.
	“Error in generating the system data” when downloading or saving a station in HW Config	The environment tag S7TMP is not set. The path c:\SDBDATAs7hwcnfkdownr00s02sdb0.dat is completely or partly invalid	Check that the paths in your Autoexec.bat are set as follows: SET PATH=”C:SIEMENSCOMMONSQLANY” SET SQLANY=C:SIEMENSCommonsqlany SET S7TMP=C:SIEMENSSTEP7S7TMP
13:77	While interpreting the system data blocks (SDBs) uploaded from the module, an error was recognized in the programming device and processing halted.	Inconsistent HW configuration in module, occurs when previous loading of SDBs into the module was incomplete or faulty.
		Options package for configuring specific modules (e.g. CPs) is not installed
13:136	The maximum possible number of slots within all inserted slaves has been exceeded by %1 slot(s).”	More slaves have been configured than permitted by the master system	Split the slaves across different segments if possible or reduce the number of slaves for the master system concerned.
13:181	Internal error:Multicomputig cannot have the type “inhomogenous”	Error in HW Config of first 4.02.x version	Add another CPU and then deleted it. The CPU is then automatically set to single-computing again
13:422	No master system is assigned to the DP slave.	Missing object	Right-click for pop-up menu, select “Add master system” and then configure the CP again as slave
13:520	The address entered is already occupied. STEP 7 has already calculated the next free address.		Confirm the address suggested by STEP 7 or enter a new address.
13:4003	Module cannot be inserted here. You can use only DP slaves in a master system.	An attempt was made to connect a device directly to the DP bus, which does not have its own interface.	In the HW catalog insert a hierarchy level for this device as DP slave
13:4040	The number of slots of the CPU or the master system has been exceeded or exhausted.	Maximum number of modules already configured.	New modules can only be slotted after deleting slaves or their modules.
13:4241	The offline configuration (%2) differs from the hardware configuration of the PLC (%3). Do you still want to continue?	An external module (interbus interfacing) from the Phoenix company was slotted	Remove external module (error can be ignored)
13:4337	Unable to set up connection to module %1 (R%3!d!/S%4!d!).	The online connection from the PG to the module (SDB addressee) could not be set up.

Error number:	Text:	Cause:	Remedy:
		Connection hardware is faulty.	Make physical check of connections (cable break,…). Repeat attempt to set up connection.
		Module (SDB addressee) is in the wrong operating mode.	Check operating mode. Repeat attempt to set up connection.
		You have specified an incorrect MPI address in the dialog box when loading to a PLC.	If you have specified an incorrect MPI address in the dialog box, then proceed as follows: Acknowledge this dialog 2. Correct the MPI address and trigger the Load function again.	1.
		PG/PC with PROFIBUS interface is connected directly with an intelligent DP slave (e.g. ET 200X BM147/CPU) and the PG/PC interface is set incorrectly.	Proceed as follows if the PG/PC interface is set incorrectly: 1. Navigate from the Windows Start bar (Start button) to SIMATIC > Step7 > Set PG-PC interface. 2. In the Access Path tab mark the PROFIBUS CP and click the Properties button. 3. In the Station Parameters group, deactivate the check box “Do not activate as only master”.
13:4343	An update is presently not possible. In one or more STEP 7 applications at least one GSE file or type file is being referenced.	In the different S7 applications there are objects (stations) open in which DP slaves are used. Thus it is no longer possible to install new GSD or type files, or even to update them.	Please close the station window in the hardware configuration and all other STEP7 applications (such as NETPRO, for example) that could access the GSD file . The Hardware Configuration application remains open however without content. Then you can install the GSD file.
13:4341	The GSE file (type file) %1 contains syntax errors. For this reason it cannot be interpreted.	STEP7 V5 + SP3 does a strict check of the GSD files. Some are not accepted, e.g. when the name is longer than 23 characters	Create a backup copy of the GSD files; open file (e.g. with Wordpad) and edit excerpt from the file Vendor_Name = “1234567890123456789012345678901234567890Machine Factory”. The name is longer than the max. 23 characters permitted. Correct to: Vendor_Name = ” xxxxx Machine Factory”. Save the file and re-incorporate it.
13:4366	Error during complete restart of the module.	An error has occurred when attempting to start the module (restart). Possibly not all the CPUs of the multicomputing station have been started.	Start the module or all the modules of the multicomputing station from the SIMATIC Manager via PLC and Operating Status.
		An error has occurred when attempting to start the module (restart). The key switch of the CPU/FM is in the STOP position	Set the key switch of the CPU/FM to RUN or RUN-P.
		An error has occurred when attempting to start the module (restart). The operating mode switch of the CP is in the STOP position	Set the operating mode switch of the CP to RUN.

Error number:	Text:	Cause:	Remedy:
13:4589	Details: (D221); cannot load SDB 7XX”.	H connections are configured in your project. The configuration of high- availability S7 connections has changed in STEP 7 V5.1. There are individual old configurations whose system data after a change can no longer be assigned to the latest configured high-availability S7 connections. This then leads to abortion of the download.	In the SIMATIC Manager delete the “System Data” folder in “CPU > S7 program > Blocks”. Then regenerate the system data in “NetPro”.
15:20533	The maximal length of debug info (max. 64 Kbyte) is reached.	The maximal length of debug info of 64 Kbyte is dependent of the system and can not be added.	The debug info will be increased very fast if there is a lot of accesses to data blocks. We recommend in refer to the debug info to reduce the access of only few data blocks.
16:5016	Parameter can not be controlled	You are trying to control an operand whose address is outside the permitted range of the controlling CPU.	Comment out the relevant line in the VAT.
		You are trying to control an operand outside the process image for which there is no module available.	It is possible to control of the operand inside the process image even if no module is slotted for the operand.
		The data block (DB) that is to be controlled is not in the CPU to be controlled. The data block (DB) is write-protected.	Load the DB into the relevant CPU.
		The data block (DB) is write-protected.	You have no write access to this DB. You must disable the READ-ONLY attribute for this DB to have write access to it.
		You are trying to control a periphery input (PI).	Direct write access to an input module is not permitted.
		With the function “Release PQ” you can only control peripheral outputs (PQ).	Direct write access to an input module is not permitted.
16:5053		In “Process Mode” it is not permitted to control or monitor I/Os.	Consider whether you achieve the desired result by monitoring the process image. Otherwise parameterize the CPU for Test Mode (Configure Hardware / “CPU Properties” dialog box / “Protection” tab).
30:13		The interface of a called block has been changed. This means that the parameters are not transferred properly to the changed block. The block call is expanded and then displayed marked as faulty.	STEP 7 up to V4.02.x: In the case of expanded block calls you delete the complete call sequence (all statements between the limiting PICTURE commands, including the red CALL / END_CALL lines) and then re-enter the CALL.
			STEP 7 V5.x and higher: In the case of incorrectly marked block calls you position the cursor in the CALL line and select the menu Edit>Block Call>Update. This adapts the block call to the new interface. Then check the new assignment of parameters.
30:15		The type object has a different time stamp to the opened block. The local symbols are displayed as pseudosymbols.	Blocks have been opened either by available users or the blocks have been copied with the SIMATIC Manager from the CPU into the OFFLINE database. However, since the CPU knows no symbols, the variable names are replaced by default names.

Error number:	Text:	Cause:	Remedy:
30:50	Error while generating the STL source.	The STL source cannot be generated, e.g. because it exists already and is write-protected, or because there is no more memory available on the drive.	Generate a source with a new name or make sure that there is enough memory available for the source to be generated.
30:484	The displayed block cannot be monitored because it does not match the block in the CPU. Do you want to download the displayed block to the CPU and then monitor it?	This is found to be caused by a discrepancy in the time stamps between the online block and the offline block and means that the blocks are different. Since the online information relating to the block sequence cannot be assigned to the individual program elements of the offline block, the block status cannot be displayed.	The programs which are generated with CFC must be downloaded from the CFC to the PLC because only this loading function guarantees that the configuration data will be consistent with the PLC data. The same loading function is also used if you compile and load the “PLC > Objects” menu command in the SIMATIC Manager or highlight the chart folder and select the “PLC > Load” function. You may not, however, highlight the block folder or individual blocks and PLC > Load, as well as copy the blocks in the “Block folder offline” in order to insert them into the “Block folder online”.
30:504	There are no parameter and local variable names available because there is a time stamp conflict between the interface of the block and the description of the parameter and local variable names.	The description of the parameter and local variable names has a different time stamp to the interface of the opened block. This is why the parameters and local variables are displayed as pseudosymbols without comments.	This conflict first arises when you open a block and interface changes made online have not been stored in the S7 user program offline and now the online block is being opened. Interface changes made offline have not been loaded into the CPU and now the online block is being opened. The interface of a function block or UDT has been changed and now the associated instance data block or the data block derived from the UDT is being opened. An online block that already has a time stamp conflict is copied offline into the S7 user program and now the offline block is being opened.
		The cause for this can be an actual hardware fault, or an interrupt conflict with another module.	In this case the customer can check whether the MPI LED lights on the CP5611 during this time. – If the LED does not light, the module could be defective or there is an address conflict on the PCI bus (though unlikely). – If the LED lights, then there is an interrupt conflict. – NT Diagnostics ->Resources. – Warning: with some modules you have to switch the computer off/on after BIOS changes. A possible remedy could also be to plug the CP5611 into a different PCI slot.
30:53	Problems occurred during the automatic generation of STL sources. See Details!	There are protected blocks in the selection list of the STL source to be generated.	Remake the selection list, but without the protected blocks. Press the Details button in the error message to obtain a Detailed List of the protected blocks.

Error number:	Text:	Cause:	Remedy:
30:202		The test that “strikes” should check whether the block is there online and offline.	Save the project under a different name.
30:473	This operation is not possible in this position.	Programming error.	Correct the code.
30:503		The type object of the block is not available, so the variable description is missing. The local symbols are displayed as pseudosymbols.	User error.
		The block is available online in the automation system, but not offline in the S7 user program.
		The block has been copied from the automation system into an S7 user program and now this S7 user program is to be opened where it did not exist before.
		A block is opened via “Available Users”. In this case there is no S7 user program linked with the automation system.
		The associated function block of an instance data block to be opened does not exist.
32:282	PG Resourcen Error, by program status of a longer FB in PLCSIM	In Step7 V5.0 SP2 with PLCSIM V4.0 under NT, project and block were opened online. This probably led to high internal use of resources.	In Step7 V5.0 SP2 with PLCSIM V4.0 do not open the project online, but select the status function from the offline project. Setting the virtual memory to 256MB does not help
33:11
33:384	The triggered action cannot be executed at this time. Check all other STEP 7 applications and exit them where necessary.	The communications module is probably already being operated with other settings (e.g. with a different transmission rate).	Please check the baud rate on the PG/PC via “Set PG/PC interface” and the baud rate of the CPU configured.
		There might be other online functions active.	Close any other active online functions (e.g. by closing the relevant windows) and try again.
		Attempt to run the firmware update of a CPU directly via STEP 7 on a CPU.	Firmware update is only possible via flash card.
33:496	The called function is not available in S7-DOS or in the CPU.		Deinstallation and reinstallation of STEP7
33:498	Internal error: Function ‘%1’ not implemented.		Delete metafiles
33:501	System error!	Attempt to get online as normal user under WinNT.
33:511	System error!	Mixed installation	Manual deinstallation of STEP 7 and S7 options packages
		NT: insufficient access rights.	You must have at least main user access rights!
		NT: main user access rights already assigned!	Check that the domain user with the main user rights has also been transferred into the Main User group on the local computer.
	EPROM: Memory card is missing

Error number:	Text:	Cause:	Remedy:
	The CP 1413 occupies the memory area 000D 0000 to 000D FFFF (complete D segment) or 000E 0000 to 000E FFFF (complete E segment). Normally MPI boards also use address areas in the D segment (from 000D C000) meaning they interfere with communication with the CP 1413.	Can occur if the new connection to the database is not set up; for example when closing and opening available users, S7db_close and open is executed. Sometimes these do not match the current connection.	With laptops, disable the power-save mode. Under WinNT check the user rights (only with Administrator rights in V3.x).
		Bus monitor Amprolyzer has been installed.	Manual deinstallation of STEP 7 and S7 options packages according to FAQ.
30:527	The interface of the multi instance call can only be updated, if the declaration of the multi instance is valid in the tag declaration table.	If you click “Yes” in the dialog box, the system corrects the corresponding entry in the detailed variable view for you.	In case it is impossible to acknowledge the dialog box with “Yes” and, hence to have the corresponding entry corrected by the system in the tag detail view, verify the system date of your PC. The system date of your PC has to be set to the current date.
			If you want to carry out the necessery changes yourself, proceed as follows: 1. Click “No” in the dialog box. 2. Eliminate the invalid multiple instance declaration by highlighting the relevant line in the detailed variable view and selecting the pop-up context menu command “Update Declarations”. 3. Position the cursor on the block call in the code section and repeat the function.
33:3100		When you have set the option “PG/PC is the only master on the bus” in the dialog by “Set PG/PC Interface” and you will make an online connection by “Display Accessible Notes” to the CP5412 A2, so you will receive this error number if not a partner is connected on this modul.
33:8242	The EPROM driver cannot support the set programming interface on this computer	PC + external prommer. Cause of error not yet known: probably a setup problem where the Registry entries are not checked.	Under HKEY_LOCAL_MACHINESOFTWARESIEMENSSINECLOGDEVICES there exist the directories MCDCENT and MCDPG. Where this is the case, when using an external prommer, you must delete the MCDPG directory. When using an internal prommer, you must remove the MCDCENT directory.
		Same message with a PG 720/740/760	Bad installation of STEP 7

Error number:	Text:	Cause:	Remedy:
33:8256	The external prommer is not connected to the corresponding port or the power supply has been interrupted.	The external prommer is not connected to the configured LPT interface.	Connect the external prommer to the configured LPT.
		The power supply of the external prommer is interrupted.	Reestablish the prommer’s power supply.
		LPT on PC faulty.
		LPT incorrectly set.	The LPT port must be set to EPP in the BIOS.
33:16399	System error by S7OTBL Server Client- Communication.	When this message appears, the S7DOS server (S7otblsx.exe or S7otbxsx.exe) doesn’t want to start.	The files S7otblsx.exe and/or S7otbxsx.exe are not available.
		This server is a relatively conventional Exe that receives data from the line as proxy for programs that want to go online. It therefore has nothing to do with databases or OLE/COM – yet.	S7otblsx.exe or S7otbxsx.exe are not in the search path? Is the server normally in S7bin or in the system directory? The S7bin directory is registered at Setup as CurrentWorkingDir of the applications. If this doesn’t work, then this message might also be displayed.
		What is the purpose of the server. S7DOS recognizes four call types, 3 of which are asynchronous. So that the application can continue to run in the case of asynchronous calls and exported if necessary, there must be a proxy that constantly “listens” to the line and receives any data that arrives. If the PLC sends data directly, only then can you start to store the applications again from the swap-out file.	Remainders in the memory after manual closing of the server. The server allocates shared memory. When it starts and finds its memory still allocated, then it discontinues the startup or if it can’t allocated the shared memory. The first case might occur if you close the server with the Task Manager and then continue without shutting down. The server needs approx. 400 KB shared memory. This should not be a problem nowadays.
		The S7DOS-DLL attempts to start the server. If this does not work, then it tries again and again. It has a timeout of 30 seconds in which time the server should be up. If nothing happens during 30seconds – no refresh of the application – then this is a clear indication of an unsuccessful server start.	In STEP 7 V5 and higher the server checks whether it has the same version as the DLL. If not, it doesn’t start.
33:16418	The monitoring time for a STEP 7 frame was exceeded.
33:16418	Timeout by wait of WM_ENDE_L7.	The monitoring time for a STEP 7 telegram has expired.
		Faulty parameterization of the access point on the MPI, L2 and H1 card or on the corresponding bus.	Correct the access point via “Set PG/PC interface” or PG/PC ONLINE card.
		There is already a communications load at the moment due to a configured S7 communication and therefore no ONLINE connection is possible.	Repeat attempt to set up connection or check the S7 connections in the S7 project.
		Cold or warm restart of communications partner.	Repeat attempt to set up connection or check the power supply of the communications partner.

Error number:	Text:	Cause:	Remedy:
33:16642	Online: Internal error – wrong configuration of telegram.	Occurs when TeleService is in operation. Error image: a TeleService connection is set up between a US-Robotics Sportster Voice 33.6 fax modem (local; analog, external) and an M1 GSM module (system side). With this constellation an online connection is set up in TeleService, the available users are displayed, but if you double-click on, for example, MPI=2 (direct), you get this error message. When you close this error message, the block container is displayed and the remote connection to the system is disconnected (295:20493).
		Error described above also occurs with a connection between US- Robotics Sportster Voice 33.6 fax modem (local; analog, external) and the Penril Data Link 19.2 modem (system side, analog, external).
33:16647	The online connection was interrupted.
33:16654	Online: The connection was broken. Check the online connection and select the instance data block again.	HW connection interrupted.	Check the connecting cables and for correct connection to the network.
		CPU has no power supply. Power supply failure.	Reestablish the power supply.
		S7-300: Group error LED (SF) lights.	Locate problem by replacing modules. One possible cause could be that the bus is unstable or the interface on the module is defective.
		Interface is already occupied by another PG connection.	Check whether a remote connection is set up.
		Power-save Management is active in the computer.	Go online again and set up a new connection. If the behavior occurs again after a short time, then deactivate the Power- save Management. Warning: in some computers this can only be done via the BIOS SETUP.
33:16656	The error occurs frequently if a station address is set which differs from the actual network configuration	The error occurs frequently if an MPI address is set, which deviates from the actual network configuration. The error can occur in particular with the following operations:	Check the connecting cables and for correct connection of the network.
		A block has been copied from an S7 program that is directly under a project and inserted in the block container of an S7 program that is under a module.	Check the PLC for power failure.

Error number:	Text:	Cause:	Remedy:
		For setting up the online connection it is no longer the MPI address in the Properties of the S7 program that is valid, but the configured MPI address of the module.	Check whether when configuring the hardware that an MPI address has been configured for the module and stored offline, under which no user exists as yet. In this case open the window for configuring the hardware. Then either adapt the MPI address in the module (by loading the configuration (see HW Config) with the changed MPI address) or change the MPI address configured offline to an existing address and save the change offline.
		A block has been opened in the “Available Users” window and then an attempt was made to save the block in a project.	Check whether the configured MPI address in the project actually corresponds to the loaded MPI configuration of the MPI network.
		For setting up the online connection it is no longer the MPI address from the “Available Users” window that is valid, but the MPI address configured in the project.	Check whether the MPI address is available in the MPI network.
		In the “Available Users” window a user has been marked and the “Monitor and control variable” function called. Then an attempt was made to save the variable, which is only possible offline in a project.	Check the “Group error message” (SF) LED of the module (CPU).
		For setting up the online connection it is no longer the MPI address from the “Available Users” window that is valid, but the MPI address configured in the project.	Check the configuration in the SIMATIC Manager and the network addresses set. (Network addresses must not be assigned twice.)
			Reset the CPU and CP, then reload the configuration and under NCM read out the address so that you can access the S7 controller online with the CP 1413.
		The block container of a CPU with several DP interfaces cannot be opened over the DP interface in the online view. This online view is however possible over the MPI/DP interface. A online connection can be built up with the function “Available station” via the DP-interface of the CPU.	1. Check the settings in the SIMATIC Manager: By clicking on “Extras > Settings > Register: View” the option “Enable MPI address to be modified” should be active. 2. Switch in the Simatic manager to online view and mark with the cursor the S7 program. Right-click, load the object properties and choose the register “Addresses: Module”. Select the correct PROFIBUS address, with which the PG is connected via the DP-interface of the CPU. 3. We recommend to notify STEP 7 of the location change of the PGs, if you have disconnected and reconnect the PC from the subnet to an other with your networked STEP 7 project. This can be executed under “Targetsystem > Assign PG/PC”.

Error number:	Text:	Cause:	Remedy:
33:16662	Online: No connection. Node does not accept the connection setup. Check the online connection and select the instance data block again.	The partner is neither a CPU nor a CP.	Check that the configuration and the actual hardware configuration match.
		The partner is not a module in the PLC.	Check the addresses given.
		The partner is a different PG or an external device.	Using the “Module Status” function check whether the selected partner is a CPU. Check whether its communications partner is slotted in the place configured (rack/slot).
		The partner cannot set up any more connections.	Close any further connections to the partner.
		Connection setup via DP interface without the CPU retaining it’s relevant SDBs.	First configure the CPU also as DP master and load the SDBs onto the CPU.
33:16914	Online: Station not online.	Power supply of the S7 is switched off.	Check whether the CPU is switched on.
		Connecting cable is not plugged in or is defective.	Check that the MPI cable is plugged in. Check the cable for breaks.
		Configured bus parameters do not match the S7 system.	Check the following bus parameters: Baud Rate, Highest User Address (these parameters must be set correctly on all stations in the network) and Timeout.
			In the Control Panel call “Set PG/PC interface” to correct the bus parameters.
			Restart MS-Windows and check the error messages of the drivers.
		Incorrect access point is selected.	Select correct access point.
		PG: hardware fault	Send PG to PG service shop to have the interface checked.
33:16917	The function is not supported by the selected hardware.	Occurs if you set up an ONLINE connection via a CP5412 A2 with the option “PC is the only master” (in the “Set PG/PC interface” tool) via “Available Users” and there is no user connected to the CP 5412 A2.	Incorrect message, the connection is set up as soon as a user is connected.
33:16944	Online: It is not found an active contact.	User not connected to the bus.	Check the connecting cables and the connection to the network. Check the PLC for power failure.
		On the PC/TS adapter the LED for correct power supply lights. This LED lights if only the 24V supply is connect and the 5V supply is missing. The PC/TS adapter however needs the 24V and the 5V power supply through the PLC.	Check the connection and whether the 24V and 5V power supplies reach the PC/TS adapter.
		The TS adapter is set to the wrong transmission rate on the MPI side.	Correct the network transmission rate under Set PG/PC interface -> MPI.
		The PC/TS adapter hardware is damaged.	Replace the TS adapter or send it in for repair.
		The wrong driver is preset under “Set PG/PC interface”.	Preset the correct driver for the TS adapter.

Error number:	Text:	Cause:		Remedy:
33:17072	Online: no hardware is found.	No driver selected or incorrect address area of the MPI interface	PG/PC interface – MPI Properties ->Select or add driver
		With Windows NT, check that the PC has an MPI-ISA card and not a CP5611.	Can be determined in the BIOS (PCI).
33:17074	ONLINE: driver is wrong configured or not valid parameter in the registry	MPI-ISA card: STEP7 version (also upgrade and corrections) -Win95 hardware recognition has been run -other drivers (also CP…) tried out -another card installed in the PG/PC -sometimes hardware is defective	installation of an	PG/PC interface – MPI Properties ->Delete all unnecessary drivers ->Re-insert and parameterize drivers
33:17075	All stations on this subnet must have the same value for the transmission rate. The interrupt may not be assigned for other hardware components. The MPI addresses in the network must be unique, meaning each address may only be assigned once. The local Station address must also not be greater than the highest station address in the programmable controller.	With this message there is usually an interrupt that is double-occupied.	Attempt to set a different interrupt once.
		Occurs with SCENIC PRO M6, Onboard Controller occupies many IRQs	Deactivate primary and secondary controllers in the BIOS.
		WIN 95 does not clearly recognize the interrupt occupied through the 3Com-Etherlink 3 (ISA) 3c0509b. This can lead to interrupt sources being double-occupied.	Select a different interrupt for MPI card.
		The reason for this can be an actual fault in the hardware, or an interrupt conflict with another module.	In this case the customer can check whether the MPI LED on the CP5611 lights during this time. -If the LED does not light, the module might be defective or there is an address conflict on the PCI bus (not very likely). -If the LED lights, then there is an interrupt conflict. -NT diagnostics ->Resources. -Warning: with some modules it is necessary to switch the computer off/on after BIOS changes Under circumstances, one remedy is to plug the CP5611 into a different PCI slot.

Error number:	Text:	Cause:	Remedy:
33:17077	Online: The setting local address of participant is assigned	The TS adapter had the same MPI address (0) as another user in the MPI network.	Via the “Parameterize Adapter” function, assign to the TS adapter an MPI address that has not yet been assigned and save it. The TS adapter has MPI address 0 as works default setting.
33:17088	Online: The selected communication driver can not be loaded. File is not found.	In V2.1 the PG/PC interface hardware is set to “none”	Select card
		Possibly wrong or no driver selected with Windows NT.	Install driver or select card.
33:17090	Logical device is not in the registry.
		The LogDev is in the Registry under the following key: HKEY_LOCAL_MACHINESOFTWARESIEMENSSINECLogNameS7O NLINELogDevice	This sequence of drivers should be of one mold, i.e. from the same generation. A mixture of drivers from different STEP7 releases is fatal!
		No, that would be too simple. As usual for such a communication, each layer is implemented as an application layer. There is therefore at least one driver for Layer 7 (s7otbldx,s7otblsx), one for Layer 4 (s7otransx) and one for Layer 2 (s7ospc2). The drivers for Layer 2 still run in the Ring 0 of Windows, the remaining drivers in the Ring 3. There is also a central program that manages the transition from Ring 3 to Ring 0 including the transferring data to and fro (s7onlinx).
		With the CP 5611: driver warped in the Registry.	Deinstall and then reinstall under “Set PG/PC interface”.
		“PG/PC is the only master on the bus” is not activated (not checked) although the PG/PC is the only master.	Active “PG/PC is the only master on the bus”.
33:17104	The version of the adapter connected does not support the bus parameters set or it is not connected to the adapter type assigned to it in the program “Setting the PG/PC Interface”.	Probably the versions of the drivers and the PC Adapter or PC/MPI card are incompatible.	Check in the PG/PC interface whether a TS adapter is addressed with the PC Adapter driver. Also check the settings of your PG and the PC Adapter (Informations you will find in the FAQ !10420976!).
33:17106	Communication to the PC/TS adapter is faulty.	The PC/MPI cable is plugged into a module that provides no power supply.	Connect external power supply.
		The connection between PC adapter and CPU is defective.	Check hardware. Warning: PC adapter needs direct connection to the CPU since no external power supply is possible.
		Connection between PC adapter and PC is defective.	Check connector pin assignments.
		The TS adapter is not yet set under “Set PG/PC interface”.	Enter the TS adapter correctly under Step7 Options –> Set PG/PC interface. Also pay attention to the properties Direct Connection/Modem Connection.

Error number:	Text:	Cause:	Remedy:
33:17108	Exit the application which is currently using the required port (COM port or USB)	Another application already occupies the serial interface or faulty setting of COM-IF upon display under NT.	With NT check in the Control Panel that STANDARD is not set for Addresses and INT in the settings of the COM interfaces under “Advanced”. If not, remove COM IF and then restart the PC. Now COM IF should be newly installed with the STANDARD option.
33:17109	The driver for the required port is currently being used by another application. Another interface parameter assignment configuration may also be in use.	The item Direct Connection has been selected in the SIMATIC Manager under Options –> Set PG/PC interface.	Select the item Modem Connection under Options –> Set PG/PC interface.
		After interruption of a TS connection the serial driver is still reserved by STEP 7.	Close TeleService and STEP 7, then restart STEP 7 first followed by TeleService.
33:17110	The interface TS adapter is set for a modem connection and there is no remote connection to a TS adapter.	After dialing into a remote system via TeleService (connection is set up), the TeleService window was minimized and PLC –> Display Available Users was selected and then this error message was displayed. The reason is probably a bad telephone line or a connection that is too slow.	Acknowledge error message with OK and simply reselect PLC –> Display Available Users. The error should then no longer appear and the available users are displayed as long as the modem connection is still set up.
33:33285	It is a copied object variant available.		Please set up the connection by closing all the S7 applications and then restarting them.
33:33540	Message from the module. Too few resources available.	Message from the PLC when reading block when, for example, two upload processes are triggered simultaneously by 2 PG.	Start Trace (Level=0x11000000)
33:33794	Illegal request of service	The CFB in the communications partner is in the wrong state.	Check the block call in the user program of the communications partner.
		PRINT block: Paper out.	Check the printer when printing via the module.
		The program instance in the communications partner is in the wrong state (cf. START, STOP, RESUME block).	Set the key switch to RUN or RUN-P before starting the module.
		When implementing a CPU with DP interfacing, you might get the following situation: a user is not available on the DP bus, the CPU remains about 30 seconds in startup and the RUN LED blinks. Then the CPU goes into RUN (as long as no I/O access to the missing I/Os puts the CPU into STOP). This is obviously a TIMEOUT effect, because the CPU doesn’t acknowledge the service in the relevant time.	Download the SDBs and restart manually.
33:34562	The service requested is not supported by the module.	The service requested is not supported by the module.	Note the restrictions of the CPU used (menu command PLC > Module status, Performance Data tab or look up the performance data in the documentation for the module used). Use a more powerful module.
		The object addressed does not exist on the module.	Check the addressing of the object.

Error number:	Text:	Cause:		Remedy:
33:42418		Message comes when executing the function RAM TO ROM: not supported by the module.	The service requested is	The module on which you wish to execute this function does not yet support this function. Note the restrictions of the CPU used (menu command PLC > Module status, Performance Data tab or look up the performance data in the documentation for the module used). Use a more powerful module.
		The addressed object does not exist on the module.	Check the addressing of the object.
33:53315	D043: Data Error: The references order is not available.	When controlling by monitoring variables, it might happen that when too many control jobs are sent to the CPU, the CPU rejects them because its buffer is too full.	Acknowledge the message and reduce the frequency of the control jobs.
33:53343
33:53346	Resources error (D062), job list is too full	The variable table (VAT) can no longer be opened although the table could be opened previously without any problems using the same program and with the same CPU. Probably the VAT concerned has not be closed correctly in the CPU.	Please switch off the power supply of your CPU and then on again. Delete jobs no longer required (for example, deleting breakpoints, terminating the function “Monitoring/Modifying Variables”, terminating the function “Program Status”). You will then be able to go online again with the VAT.
33:53347	(D063) Resources error: the trigger event is occupied.	It is no longer possible to monitor a block. This behavior is triggered by irregular termination of the process in the operating system.	1. Unplug the online cable of the CPU and wait at least 1 minute. It is not enough to unplug the CPU just briefly. 2. Shut down your programming device and wait 1 minute before switching it on again. A simple reboot is not always sufficient.
		Message from the module. This function cannot be executed at the moment, because the resource required is already occupied. There are also too many test functions activated at the same time and the resources available on the module are exhausted.	Delete the jobs that you no longer need (e.g. delete stop points, close the “Monitor/control variables” function, close the “Program Status” function).
33:53772	Note the restrictions of the module being used.	Message from a module.	Note the restrictions of the module implemented. (See also in the Message from Modules area.)
33:53790	The module to be assigned parameters is currently busy assigning parameters to subordinate devices. It was been by the modules: 416-2DP + CP443-5 Extended		Remedy: reset the CP via Online HW Config and Download HW Config. Repeat the module download when all stations and field devices on the bus are started up and in operation. To ensure that the module to be downloaded temporarily cannot assign parameters to subordinate devices, remove the interconnecting bus cable from the DP interface for the duration of the downloading process.
			In the case of an IM 467, you must do a POWER OFF/ON. This resets the IM and the HW Configuration can now be downloaded.

Error number:	Text:	Cause:	Remedy:
33:53797	The distributed I/O system data block is structured incorrectly.	A diagnostics address outside the address area has been specified. (For example, Win AC lite was installed.)	Change the diagnostics address.
33:53798	A mismatched CPU type or an internal structural error has been detected during block analysis.	When evaluating the blocks, an incompatible CPU type or internal structure error was detected.	Please check whether the type (MLFB) of the CPU that you have configured matches the CPU type onto which you are loading. Match the CPU types and reload. If this is not the case, nevertheless regenerate the configuration data (blocks) and load the data onto the CPU. Please check that you are using the latest version of the configuration software (with the latest Service Pack).
33:53824	D204: The rules of coordinations were broken.	When attempting to load the system data, there was still a variable table open online.	Close the variable table and retransfer the system data.
33:59906	The communication software (S7DOS) and the interface module (CP) have not the same protocol.	The customer has a STEP 7 V5+SP1 + new PDM and a CP 443-5 Ext > V2.7. The new protocol RPC 7 that is used for data record routing between the CP and S7DOS. Unfortunately versions up to version V2.7 of the CP do not have this function.	Upgrade CP 443-5 to a version >V2.7.
		The user is implementing the right components STEP 7 V5 + SP2 + PDM, but has a CP that does not include the DSGW.	Check the configuration and replace the CP implemented with a different CP that includes this function.
34:11	Compiler information: handle not valid.	When monitoring an empty network with the LAD/FBD/STL editor.	Delete empty network.
34:21	Compiler information: element not found.	The element could not be found in the referenced database.	Check the spelling of your search key and your database reference.
34:38	Compiler information: Compiler error
34:39		You have attempted to rename a variable, but the name is already being used.
34:152	Reference data could not be generated.	Error in the database.	The project can be correct+D191ed with “Save As with reorganization”.
34:168	The moduls in the comand structure are protected and can not be generated.	One or more direct or indirect reference module is know how protected and can not be generated	Please deactivate the option “Include reference blocks” in the menue “Generate source …”. You have to create the list of the moduls via manual without the protected moduls.
34:173	At least one symbol assignment has changed	If you copy a symbolically addressed block from the library of an S7 project into another project and after you open the block. In the original project you generate an STL source from the block.	1. Please make sure that the source is generated with the setting “absolute”. 2. Copy the source into the new project; the project can be configured as symbolically addressed. 3. Now compile the source and so generate the block. After that you can adapt the symbols as required without the behavior described above occurring.

Источник