OK, that verifies that the terminal is a PanelView Standard. I believe that the "P1.CTK" on the information screen means that it's equipped with a DeviceNet daughtercard, but a photo or the exact part number would be conclusive.
The *.ACD file is for a 1756-L63 with Version 13 firmware, so you're probably running RSLogix 5000 in Windows XP or Windows 7, and have RSNetworx software for that generation.
Your test program also doesn't appear to have used the DeviceNet Tag Mapping Tool, which created logic that mapped out data from each DeviceNet scanlist entry to ControlLogix tags, so you're starting from scratch there.
You will need the 1756-DNB Scanlist to know where in the Local:4:I.Data[x] and Local:4:O.Data[x] array tags the PanelView data goes.
In the PanelBuilder32 software itself, the Input and Output images are really pretty straightforward syntax.
They are literally
I:<word/<bit> and
O:<word>/<bit> for each Word of the I/O Assembly. The I/O assembly can be up to 64 16-bit Words in each direction.
To my knowledge the PanelView's syntax was always 16-bit on the DeviceNet side, since it was built to work with the 16-bit SLC-500 and PLC-5 DeviceNet scanners. When you use it with a 32-bit DeviceNet scanner with a ControlLogix, you just have to account for two Words in every I/O image DWord.
RA
Knowledgebase Article 32024 discusses that a little bit, but it really is just as simple as "copy 32-bit DINT data into a 16-bit INT tag array if it helps you understand and use it better".