adccommunitymod (AutomationDirect) asked a question.
Created Date: October 25,2004
Created By: loubie
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
I'm tryimg to get my first 205-1 off the ground and when I go into Program Test Mode I get errors 471 (duplicate coil reference ...) and 431 (Invalid ISG/SG address). Same thing happens when I check Syntax with I/O config... I have all duplicate coils OROUTed yet still gives me errors 471 on every coil address. Regarding the 431 error, I understood the stages have default addresses therefore I just called the "S(number) ". Why is it reporting incorrect address? The module configuration is from left to right: 250-1; F2-04AD-2; d2-16ND3-2; D2-16ND3-2; D2-16TD1-2;H2-ECOM. No real devices are connected to the modules.
Created Date: October 25,2004
Created by: loubie
I'm tryimg to get my first 205-1 off the ground and when I go into Program Test Mode I get errors 471 (duplicate coil reference ...) and 431 (Invalid ISG/SG address). Same thing happens when I check Syntax with I/O config...
I have all duplicate coils OROUTed yet still gives me errors 471 on every coil address.
Regarding the 431 error, I understood the stages have default addresses therefore I just called the "S(number) ". Why is it reporting incorrect address?
The module configuration is from left to right: 250-1; F2-04AD-2; d2-16ND3-2; D2-16ND3-2; D2-16TD1-2;H2-ECOM. No real devices are connected to the modules.
Created Date: October 25,2004
Created by: hanziou
It always tells you you 've got duplicate coil reference, if the same coil is on the right side more than once. I 've had that happen using SET and RST. If the ladder logic is right, you'll be okay.
RE 431 Error: ????
Created Date: October 25,2004
Created by: loubie
Thank you. One down, two more to go...
When should I be able to select 1 Step and Breakpoint, they appear inactive under both Program Test and Run Test.
Can the same subroutine be called, (GTS K1), from within different stages? (provided only one of those stages is active at a time and the subroutine LBL K1 is placed after the End Rung)
Created Date: October 25,2004
Created by: bcarlton
1. While the S(tage) numbers do exist, a Jmp to a stage is checked during the preliminary 'pre-scan ' before actually entering the run mode. If there is a Jmp to a stage which isn't actually used in the program then this may be the cause of the error.
2. You can go to a subroutine (GTS) as often as you wish to, even from two stages which are both active. As long as the total scan time doesn't trip the watchdog timer.
Created Date: October 26,2004
Created by: loubie
Interesting because the stages reporting the address error were those in the subroutine. I changed the way to call it (i.e. without using GTS/LBL, but kept the logic within the subroutine), and now it works. Does that mean it doesn't like stages within a subroutine or is there a detail that I'm missing such as "there shouldn't be logic between the Lbl and the first stage, etc...? " . Thanx for your help
Created Date: October 26,2004
Created by: bcarlton
Hmm, I 've never implemented stages in a subroutine. I 've set or reset them from within a subroutine but never actually had the stage itself in the sub. Here's the info on the E431 fault:
INVALID ISG/SG
An ISG or SG instruction must not be placed after the end statement (such as inside a
subroutine).
Created Date: October 26,2004
Created by: loubie
Right on it. When I used the GTS I had to have the logic after the END...
I couldn't find that more extensive error explanations in the manual...??
Thank you
Created Date: October 26,2004
Created by: franji1
If you are using stages inside subroutines you are mis-using stages.
Stages should not be viewed as subroutines - subroutines should not be viewed as stages.
Stages are very high level control - enabling/disabling sections of code. Subroutines are places to do common tasks from multiple places.
If you are familiar with operating systems - think of stages as processes which are enabled or disabled per PLC scan. Subroutines are literally that - "functions " that are "called ". You can "enable " or "disable " stages from a subroutine (e.g. SET S10 or RST S12 instructions within an SBR), but it makes no sense to actually have stages inside a subroutine.