I have set up a ConnectPort X2D and have the latest POST and EOS firmwares installed.
The X2D has a RealPort option in the network settings, and the release notes for this version of the firmware says that it supports simultaneous use of Python and RealPort.
I installed RealPort on my PC and set it to COM2, but when I try to connect via X-CTU (or other apps that can open COM2), the connection fails and I get these messages in the ConnectPort’s event logs:
2014-11-25 17:56:10 netcx Server 0: realport connection from ‘192.168.1.150’.
2014-11-25 17:56:10 netcx Server 0: Open serial 1.
2014-11-25 17:56:10 netcx Server 0: Open serial 1: failed.
2014-11-25 17:56:10 netcx Server 0: Open serial 1.
2014-11-25 17:56:10 netcx Server 0: Open serial 1: failed.
2014-11-25 17:56:10 netcx Server 0: Open serial 1.
2014-11-25 17:56:10 netcx Server 0: Open serial 1: failed.
2014-11-25 17:56:10 netcx Server 0: Open serial 1.
2014-11-25 17:56:10 netcx Server 0: Open serial 1: failed.
2014-11-25 17:56:10 netcx Server 0: Open serial 1.
2014-11-25 17:56:10 netcx Server 0: Open serial 1: failed.
2014-11-25 17:56:12 netcx Closing server 0.
What am I doing wrong?
When I go to Device Operations in for the embedded XBee module, I can click Identify Device and the lights on the gateway blink 5 times, as expected.
I’m running RealPort on Windows 7, but I don’t think that matters. The problem seems to be with the ConnectPort.
Versions:
POST = 1.1.3 (release_82002548_B)
Firmware = 2.17.1.0 (82002549_F1)
XBee module firmware = 0x21a7