# Is I2C address displayed correctly? \[SOLVED\] **URL:** \ **Category:** Extensions\ **Created:** [June 15, 2022, 1:19pm UTC](https://discuss.saleae.com/t/is-i2c-address-displayed-correctly-solved/1646 "2022-06-15T13:19:22Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jackhab](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/jackhab/32/1108_2.png) [@jackhab](https://discuss.saleae.com/u/jackhab)\ **Post date:** [June 15, 2022, 1:19pm UTC](https://discuss.saleae.com/t/is-i2c-address-displayed-correctly-solved/1646/1 "2022-06-15T13:19:22Z")
I’m recording the I2C access to IO expander slave at I2C address 0x40. The device works OK and I can see correct transaction at pulse level but why I2C analyzer says “Setup Write to [0x20]” instead of 0x40? ![Clipboard](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/2X/d/d8ae81dba3233b61ac483e5deb2bad1c755a3879.jpeg) ---
**Author:** ![jackhab](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/jackhab/32/1108_2.png) [@jackhab](https://discuss.saleae.com/u/jackhab)\ **Post date:** [June 15, 2022, 2:25pm UTC](https://discuss.saleae.com/t/is-i2c-address-displayed-correctly-solved/1646/2 "2022-06-15T14:25:28Z")
Well, I just found I needed to add I2C 8-bit Address Display analyzer to show the address in correct format. ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [June 15, 2022, 7:26pm UTC](https://discuss.saleae.com/t/is-i2c-address-displayed-correctly-solved/1646/3 "2022-06-15T19:26:14Z")
@jackhab Ah yes, sorry for the initial confusion, but I’m glad you found the workaround. > **[Viewing I2C Addresses as 8-bit](https://support.saleae.com/faq/technical-faq/viewing-i2c-addresses-as-8-bit)**