How to address this issue?...
I've had to jump this hurdle a few times in the past...
677524 - PanelView 800: Tag Addressing with MicroLogix 1400 Controller
Access Level: Everyone
The PanelView 800 HMI terminals are designed to integrate natively with the Micro800 controllers. For this reason, they address controller I/O in groups of 16 bits of data. For the MicroLogix 1400 controllers, the embedded I/O is represented by a virtual Slot 0 and so adds a degree of complexity for the PanelView 800 in addressing beyond the embedded I/O, but it is doable.
The embedded Slot 0 is made up of 8 groups of 16 bit words for the Inputs -
I:0.0 - I:0.7
Where I:0.0 =
I: = Input
0. = Slot 0
0 = 16-bit Word 0
...Up to I:0.7 =
I: = Input
0. = Slot 0
7 = 16-bit Word 7
The embedded Slot 0 is made up of 6 groups of 16-bit words for the Outputs -
O:0.0 - O:0.5
Where O:0.0 =
O: = Output
0. = Slot 0
0 = 16-bit Word 0
...Up to O:0.5 =
O: = Output
0. = Slot 0
5 = 16-bit Word 5
The PanelView 800 is essentially seeing the first 8 groups of 16 bit input data as groups 0 - 7. This means that the next possible group for the controller to look for input data is group 8. So, if we place for instance a 16 point input module as the first expansion module, the controller will address this module as I:1/0 (16 bits). But for the PanelView 800, we must assign addressing for this module starting at I:
8/0 to I:
8/15, which represents group 8 as far as the PanelView 800 is concerned. So controller input I:1/0 is now represented by I:8/0, and so on. Another way to look at it is that the PanelView 800 is now seeing groups 0 - 8, which includes the embedded inputs and the expansion input module.
For your application though, you have a 16 point output module as the first and only expansion module, yes?
Here we must first look at the embedded output addressing - as the embedded outputs are represented by 6 groups of 16 bits (0-5). Here we would say that the next group of 16 bit output data the PanelView 800 will look for is group 6. So if we add a 16 point output module as the first expansion module, the controller will address this module as O:1.0 (16 bits), but the PanelView 800 will address it as O:6.0 (16 bits).
Further, if we change the 16 point output module to a 32 point output module, and still as the first expansion module, the first 16 outputs will be addressed in the PanelView 800 as above - O:6.0 (16 bits) and the second 16 outputs will be addressed via the next group number - O:7.0 (16 bits).
Likewise if we changed a 16 point input module as the first expansion module to a 32 point input module, the first half of the module is as before - I:8/0 (16 bits) and the second half would be - I:9.0 (16 bits).
There are other "gotcha" scenarios to using this configuration but I'll not expand any further here.
Regards,
George
