# S2B Pro does not but S2C Pro does throw invalidOperatingModeException

**URL:** <https://forums.digi.com/t/s2b-pro-does-not-but-s2c-pro-does-throw-invalidoperatingmodeexception/19954>\
**Category:** Python\
**Tags:** xbee-pro-s2b, api-mode, xbee-pro-s2c, xbee-python\
**Created:** [October 25, 2018, 10:47am UTC](https://forums.digi.com/t/s2b-pro-does-not-but-s2c-pro-does-throw-invalidoperatingmodeexception/19954 "2018-10-25T10:47:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BigBoomBlueAsh](https://avatars.discourse-cdn.com/v4/letter/b/c5a1d2/32.png) [@BigBoomBlueAsh](https://forums.digi.com/u/BigBoomBlueAsh)\
**Post date:** [October 25, 2018, 10:47am UTC](https://forums.digi.com/t/s2b-pro-does-not-but-s2c-pro-does-throw-invalidoperatingmodeexception/19954/1 "2018-10-25T10:47:05Z")

</div>

Trying to swap out an ancient S2B Pro radio for a new S2C Pro radio. Used XCTU to establish identical function set, PAN, baud etc. New radio works fine on XCTU. When deployed on Raspberry Pi3B using Digi’s Python3 XBee library under Python 3.5.3, new radio throws invalidOperatingModeException:\_Could\_not\_determine\_operating\_mode when attempting to execute device.open(). (of course the old radio does not throw any errors.) Why? What to do?

Old Part No: XBP24BZ7PIT-004-revF  
New Part No: XBP24CZ7PIT-004-revF