![SWTB_logo_rgb_color_mode-wPadding-2000x961.png]](https://help.softwaretoolbox.com/hs-fs/hubfs/SWTB_General/Images/Press_Kit/SWTB_logo_rgb_color_mode-wPadding-2000x961.png?height=50&name=SWTB_logo_rgb_color_mode-wPadding-2000x961.png){kind=logo}
TOP Server GE CCM Protocol Addressing
Can the TOP Server GE CCM driver use the same addressing as the GE Fanuc CCM2 I/O server from Wonderware version 7?
The current driver will now accept the Wonderware tag names without having to make the modifications below.
The outputs will be read only by default. The way they need to be addressed is below. Changes can be made quickly with a DB Dump and modification of the CSV file in Excel.
| Device | Address Range | Data Type | Access |
| Discrete | I1 to I12288 | Boolean | Read Only Inputs |
| I1 to I12281(every 8th bit) | Byte, Word | ||
| I1 to I12273(every 8th bit) | Short, BCD | ||
| Discrete | Q1 to Q12288 | Boolean | Read Only Outputs |
| Q1 to Q12281 (every 8th bit) | Byte, Word | ||
| Q1 to Q12273 (every 8th bit) | Short, BCD |
The difference in addressing is not a method, but depends on what type of I/O address you are trying to communicate to in the Device. Extended I/O are different then regular I/O and can be written to and require the Hex O to F and + after the I or O and then the address offset number.