I am looking at Lad2 rung 5 and 6 this is my BTR and BTW
Take a look at N7:66 thru n7:82 this is my ch. 1-16 I am reading ch. 1 and 2 but not the rest.
Now take a look at n7:63 and n7:64 in binary and tell me what you think?
There is data in all of those points, are you saying the values do not change?
While online, do you see the BTR instruction cycling?
Now for the BTW to configure the card (I did not pick apart all the config data, these comments regard the way it is programmed):
It looks like the BTW is conditioned by the module to only happen if the card requests it. So, put in a brand new card which has never been configured, and this bit will go true. The BTR will read this bit (N7:62/0), the BTW will execute, and as long as it is the right size for the IFE card revision level, the BTW will get a DN (done bit), and the configuration will take effect.
Now, if the card has a valid configuration in it (the card might be used or repaired, and will keep the last configuration indefinitely AFAIK), then it will sit there happily interpreting the data as it thinks it should which may not fit your present application.
You may want to try forcing the BTW to execute with a temporary edit:
While online, delete the BTR rung and change the XIC N7:62/0 to XIO N7:260/15 on rung 6. Then test the edits for a couple of seconds and watch to see that the BTW executes and gets done, then untest the edits, and cancel them to put your logic back how it was.
If the above works for you:
Since this problem could return anytime a used module is swapped in that spot or any other slot similarly programmed, you may want to consider an alternate means to trigger the BTW. You could have a maintenance screen on an HMI or SCADA system that would allow qualified personnel to force the configuration to the modules as one example.