Persistent Stk Overflow, unable to clear.

[SMC]

im attempting to piece a disinfection system back together, and picked up two V130 RA22s to replace the v120s that went bad. I pulled the program off of the working v120s, converted the program to work with the v130s, corrected the warnings it through about having multiple  HMI calls in the same net by moving them to new nets. updated the OS for the v130s, and downloaded the program. It booted up fine the first time, i pressed a button to change the menu screen and it threw STK Overflow. Power cycled the unit, it persisted. downloaded a blank program, then the original program, still persisted. Not sure what else to do at this point.

one controller throws subroutine error at e9 which is under Screen Modules > Main Menu Scn

the other throws 11f which is under Screen Modules > Main Menu 2 Scn

 

Im currently trying to figure out how to clear the stk overflow, and what the program is doing to cause the error. Running  it on the v120s dont create the error, just seems to be the v130s. Any help is appreciated.

Bank Controller conv 130.vlp

[kratmel]

Hi,

2 hours ago, SMC said:

It booted up fine the first time, i pressed a button to change the menu screen and it threw STK Overflow. Power cycled the unit, it persisted. downloaded a blank program, then the original program, still persisted. Not sure what else to do at this point.

download blank project and try  Init & Reset via visilogic communication menu.

Some tips:

1) Please post  V120 program;

2) Please change -|  |-   contact to  -|P|-  to use the function Load HMI Display.

3) In posted program present many warning  about  ladder  -  V120 and V130 is from different series.

Some net from V120 maybe do not work in V130.

Something like 

changed to

solve warning problems;

4) Please read this Help topic,  some net from V120 program deleted if program converted to V130 

 

[Gabriel Franco]

As Kratmel mentioned, change all continuous HMI display calls to single call.

Change from this:

To this:

[Ausman]

As well as Gabriel's point, a piece of info in Help that I suggest is a MUST read is "Program Sequencing: Modules, Subroutines, Labels & Jumps" paying particular attention to the Runs HMI Program info at the bottom.