I agree with the last few posts, interesting though, I don't expect you to try it but let's look at this in a number of ways.
According to your previous posts this is an existing system but there is a problem that it is not working, assume PLC is in run mode with no errors then it is probably just some sensor or input or wiring that is not in place so it will not start or it stops at a particular point. in this case, if you can monitor using TIA that seems to produce valid code then thats all you need it for.
option 2, Do as Jesper posted remove the red lines, & BLD instructions recompile & see if it matches the PLC (may come up with warnings regarding timestamps but providing there are no differences in actual code you could keep it as a backup, do suggest you do keep the original upload in Classic & the TIA version as it seems the classic accepts the hardware config but not the translated code. So it could be possible if things go wrong you will only have to download the PLC code not the hardware (if TIA allows it).
Option 3, in Classic do the mods, download the code if it seems to work without problems then take another snapshot in Classic.
I do suggest you find the fault first I doubt it is program unless for some reason it is corrupted but not detecting the code error, this I would think is highly unlikely, what with checksums & illegal code detected in the PLC it would surely shut down.
In saying that, I have had a PLC that the code had changed, no possibility of anyone but me going on-line, the code had changed if I remember correctly 3 contacts had changed, can only assume the checksum was the same for the two different versions, almost certain it was corruption that although seems impossible made it valid code. & no, only I had the code, it was password protected (only I knew it as I had changed it a couple of months previously), no lan connection & laptop was always with me as I used to keep it even on holiday to remote in to our Scada systems.
According to your previous posts this is an existing system but there is a problem that it is not working, assume PLC is in run mode with no errors then it is probably just some sensor or input or wiring that is not in place so it will not start or it stops at a particular point. in this case, if you can monitor using TIA that seems to produce valid code then thats all you need it for.
option 2, Do as Jesper posted remove the red lines, & BLD instructions recompile & see if it matches the PLC (may come up with warnings regarding timestamps but providing there are no differences in actual code you could keep it as a backup, do suggest you do keep the original upload in Classic & the TIA version as it seems the classic accepts the hardware config but not the translated code. So it could be possible if things go wrong you will only have to download the PLC code not the hardware (if TIA allows it).
Option 3, in Classic do the mods, download the code if it seems to work without problems then take another snapshot in Classic.
I do suggest you find the fault first I doubt it is program unless for some reason it is corrupted but not detecting the code error, this I would think is highly unlikely, what with checksums & illegal code detected in the PLC it would surely shut down.
In saying that, I have had a PLC that the code had changed, no possibility of anyone but me going on-line, the code had changed if I remember correctly 3 contacts had changed, can only assume the checksum was the same for the two different versions, almost certain it was corruption that although seems impossible made it valid code. & no, only I had the code, it was password protected (only I knew it as I had changed it a couple of months previously), no lan connection & laptop was always with me as I used to keep it even on holiday to remote in to our Scada systems.