snordvikqplas
Supporting Member
Hello all
I have attached only a section of code (hence all of the eeee's) for a program I wrote a few years back and I am in the process of a final polish. The program has been working fine in production, however there is one thing that has always bugged me and I do not have an answer for it.
I basically wrote a program that stores a certain number of lengths in integer files, once the desired number of initial lengths (INTs) have been collected the program will shift all of the values down one space and bring in the new value.
Program would add all these values in order to get a "Running Rate" etc...
What I do not like and I think that I am mistaken in my code starts at rung 0001 in the attached section.
I used a ONS to execute several MOVs and DIVs only one time and at the end is an OTE. This OTE would advance to the next section where the shift would happen.
Notice the timer that I used to delay execution of rung 0004, I need this because all of the calculations and moves in Rung 0001 would not complete before the OTE caused the next set of rungs to be executed.
All I have been able to come up with as an explanation is the amount of time it takes for MOVs and DIVs to execute is longer than the OTE.
This is not a big deal in that the program works and I am able to execute exactly how I want, I am just throwing this out to some of you guys that have more experience and may be able to tell me that what I wrote is fine or explain why it happens.
Thanks in advance
I have attached only a section of code (hence all of the eeee's) for a program I wrote a few years back and I am in the process of a final polish. The program has been working fine in production, however there is one thing that has always bugged me and I do not have an answer for it.
I basically wrote a program that stores a certain number of lengths in integer files, once the desired number of initial lengths (INTs) have been collected the program will shift all of the values down one space and bring in the new value.
Program would add all these values in order to get a "Running Rate" etc...
What I do not like and I think that I am mistaken in my code starts at rung 0001 in the attached section.
I used a ONS to execute several MOVs and DIVs only one time and at the end is an OTE. This OTE would advance to the next section where the shift would happen.
Notice the timer that I used to delay execution of rung 0004, I need this because all of the calculations and moves in Rung 0001 would not complete before the OTE caused the next set of rungs to be executed.
All I have been able to come up with as an explanation is the amount of time it takes for MOVs and DIVs to execute is longer than the OTE.
This is not a big deal in that the program works and I am able to execute exactly how I want, I am just throwing this out to some of you guys that have more experience and may be able to tell me that what I wrote is fine or explain why it happens.
Thanks in advance