It's your place to connect with experts and peers, get continuous support, and share knowledge.
Contact SchneiderCommunity.Support@se.com if you have any questions.
You can subscribe to this forum after you log in or create your free account..
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.
Already have an account? Login
. Last Modified:
An issue puzzled me for a long time, the b3 program stopped at line E, but not go back to the specify line, the program code like below
Numeric input A
Numeric output B
if A is on then B=on else B=off
go to 1
I guested the program go to line E because write value to another 3rd party device, the program should go to line 1 but stopped at line E, the program state is enabled and status is running.
I never encountered this issue with Continuum b3 program, but do that with SBO b3 script program. .
Anyone can comments why the program does not go back?
Is this a fall-thru program or looping?
It is a Looping program
Please reference the code below:
Go to E
You can change "Go to E" to "Go to 1" if you require the execution to be different.
Thanks for reply, But I do not understand why "Go to E" is necessary? I think the program will go to line E in default when there is a fault at any line.
Not need for goto E, that happens automatically when the PE interpreter encounters an error.
Not need for state=enabled either, line E keeps the program from getting disabled, that's its purpose
The program appears to be stopped at line E, because if the condition that causes to go to E persists then it will constantly jump to E, typically you want to have a delay in E
If ts > 30 then goto 1
Thank you ,Abraham, I will have a try and change the code.
Register today for FREE
Already have an account?Login