If have a SST- PFB-SLC, I am very familiar with how it works.
I didn't know there was a Profibus DP Panelview till your post. I guess there is always new stuff to learn. I read the Panelview Profibus DP documentation quickly, not thoroughly. What you need to do is to map the 16 input and output register of the Panelview into 16 of the 32 input and output registers. This is done when you load the .GSD file and configuration into the Profibus DP master. You should be able to see the data in the input registers change when the Panelview sends a new command or block of data. The first word of the 16 or 15 register that comes back is a command that lets the ladder know which data is in the other 15 registers. The ladder must then activate ladder to copy the returned data to the correct locations in the PLC.
The SST-PFB-SLC also has M0 ( output ) and M1 ( input ) registers that are accessed using COP commands. I don't recommend using M0 and M1 files for any regular transfer of data because there is a big time penalty. The Profibus DP master CPU and SLC cpu must arbitrate for access to this memory and only one processor can access M file memory at a time.
When talking to the SST guys, you can't expect them to know anything about the Panelview or its method of multiplexing data. They should be able to tell you how to load the Panelview .GSD file. They should have been able to tell you that the data will appear somewhere in the 32 input or 32 output registers or in the M files. They should have told you to use the 32 input and output register if possible because they are much faster to access than the M files. The SST guys should have told you that you don't use MSG blocks or block transfers, you only need the COP command if you are copying many words to or from the M files.
The Rockwell guys can't be expected to know anything about the SST card. They should be able to supply the .GSD file and clarify how the multiplexing occurs and that it is the PLC's ladder that must look at the command and from that determine what is in the other registers.
It is not clear to me if the Panelview is continuously cycling through all 15 or 16 blocks or if the block or command only changes when a button activates the block.
What I found disappointing is that the Panelview only transfers data at 1.5M bps. This means that all the devices on the bus are limited to 1.5M bps. There is no excuse for not supporting 12M bps since the two most popular Profibus slave interface chips support auto bauding from 9600 bps to 12M bps. Why cripple a product when it is so easy to do it right?