Rslogix5000 how to troubleshoot indexing JSR

[tarrant79]

Hi, I am dealing with a single SBR subroutine thats handed 1 input paramter UDT P.x multiple times: (Pump) P.1/2/3/4/5. I JSR into the same routine for all pumps with handing it INPUT=P.x and RET=P.x so I process the UDT P.x for each index and then update the P.x with the return parameter. The only problem is I can only see the last index into the called subroutine to troubleshoot.


Ive been getting around it by, running all JSRs, and then coming back around to do a 2nd JSR call for whatever Pump I'm trying to troubleshoot. I just figure theres got to be a better way....
Thanks


JSR Pump_xx 1 P[1] P[1]
JSR Pump_xx 1 P[2] P[2]
JSR Pump_xx 1 P[3] P[3]


JSR Pump_xx 1 P[2] P[2] =To see Pump[2] executed in the routine Pump_xx to troubleshoot.

 

[jdbrandt]

Hi, I am dealing with a single SBR subroutine thats handed 1 input paramter UDT P.x multiple times: (Pump) P.1/2/3/4/5. I JSR into the same routine for all pumps with handing it INPUT=P.x and RET=P.x so I process the UDT P.x for each index and then update the P.x with the return parameter. The only problem is I can only see the last index into the called subroutine to troubleshoot.


Ive been getting around it by, running all JSRs, and then coming back around to do a 2nd JSR call for whatever Pump I'm trying to troubleshoot. I just figure theres got to be a better way....
Thanks


JSR Pump_xx 1 P[1] P[1]
JSR Pump_xx 1 P[2] P[2]
JSR Pump_xx 1 P[3] P[3]


JSR Pump_xx 1 P[2] P[2] =To see Pump[2] executed in the routine Pump_xx to troubleshoot.

In the OldenDays (*), we used to put StatusFlagBits in multi-used routines, for situations like this. Its tempting to leave such troubleshooting/de-bugging stuff out, when you develop...but at the first glitch makes it worth it.
(*) FORTRAN 4

 

[widelto]

Maybe I am wrong but what about if you convert your JSR code into an AOI.

 

[tarrant79]

I was avoiding AOIs so I can keep online editing of a SBR.