fixed issue #859
fixed issue #859

NMGRL/pychron,UManPychron/pychron,USGSDenverPychron/pychron,USGSDenverPychron/pychron,NMGRL/pychron,USGSDenverPychron/pychron,UManPychron/pychron,UManPychron/pychron,USGSDenverPychron/pychron,NMGRL/pychron,UManPychron/pychron,NMGRL/pychron