RMA
Member
First off, apologies for forgetting to switch to English before making the screen dumps! For those (few) who don't know:
U = A
SPB = JC
Basically I've got three curiosities here: data Bits not changing in the STA column in View, RLOs being set incorrectly and Data Bits being displayed incorrectly in a VAT (at least according to the logic of the program). I strongly suspect that those last two are linked somehow.
We've got a statistics PC which records all the error messages coming from the production line. Unfortunately a lot of the messages are in correct, so I wanted to write a short program to increment through the 4 Bytes of error Bits for each station at 2 second intervals, so that we could get a complete list of the error messages held in the PC. The program is called at the end of OB1 and Bit M777.7 is used to signal whether to run the test or just exit and M777.6 is used as a First-Time-through indicator.
In the first screen dump, everything looks normal - M777.7 is "0" and M777.6 gets reset (apparently) and the jump to "exit" is executed.
In the second picture, M777.7 is set to "1", but in the STA column, the value is still shown as "0". However the RLO for the UN query has correctly changed to "0" and the jump is not executed. Unfortunately though, although M777.6 has not been set in the program and #Meldung_Start has not been preloaded with "90" for the start of the Message area, the RLO for the SPB - Jump command has been set and the program continues from "next". This is almost certainly connected with the fact that in the VAT M777.6 is shown as being set!
Just for the record, I'm well aware that Step7 doesn't always display single passes through a code block, but in this case I'm relying on the fact that #Meldung_Start is still "0" to concluded that M777.6 should still be FALSE.
The memory Bytes 776 - 777 are definitely not being used elsewhere in the program - apart from the fact that I've double checked for overlapping access in X-Ref, before I wrote this code the highest used Memory Byte was somewhere around MB350.
Anybody got any idea what's going on - either with the curious displaying of data or where I've gone wrong in the program, in case I've got to the stage of not being able to see the wood for the trees!
Oh, by the way, the BEA near the bottom of the screen got added after the CPU went into STOP first time round, so that I could examine what was going on, in peace - I didn't want to risk forgetting to remove OB121 again!
U = A
SPB = JC
Basically I've got three curiosities here: data Bits not changing in the STA column in View, RLOs being set incorrectly and Data Bits being displayed incorrectly in a VAT (at least according to the logic of the program). I strongly suspect that those last two are linked somehow.
We've got a statistics PC which records all the error messages coming from the production line. Unfortunately a lot of the messages are in correct, so I wanted to write a short program to increment through the 4 Bytes of error Bits for each station at 2 second intervals, so that we could get a complete list of the error messages held in the PC. The program is called at the end of OB1 and Bit M777.7 is used to signal whether to run the test or just exit and M777.6 is used as a First-Time-through indicator.
In the first screen dump, everything looks normal - M777.7 is "0" and M777.6 gets reset (apparently) and the jump to "exit" is executed.
In the second picture, M777.7 is set to "1", but in the STA column, the value is still shown as "0". However the RLO for the UN query has correctly changed to "0" and the jump is not executed. Unfortunately though, although M777.6 has not been set in the program and #Meldung_Start has not been preloaded with "90" for the start of the Message area, the RLO for the SPB - Jump command has been set and the program continues from "next". This is almost certainly connected with the fact that in the VAT M777.6 is shown as being set!
Just for the record, I'm well aware that Step7 doesn't always display single passes through a code block, but in this case I'm relying on the fact that #Meldung_Start is still "0" to concluded that M777.6 should still be FALSE.
The memory Bytes 776 - 777 are definitely not being used elsewhere in the program - apart from the fact that I've double checked for overlapping access in X-Ref, before I wrote this code the highest used Memory Byte was somewhere around MB350.
Anybody got any idea what's going on - either with the curious displaying of data or where I've gone wrong in the program, in case I've got to the stage of not being able to see the wood for the trees!
Oh, by the way, the BEA near the bottom of the screen got added after the CPU went into STOP first time round, so that I could examine what was going on, in peace - I didn't want to risk forgetting to remove OB121 again!