ConnectPort X2 can't read AT values from module

Hi - newbie question (sorry)

I have a connectport x2 900hp - installed and worked fine out of the box.

I ‘fiddled’ about (just learning) and now I have an issue I’ve not been able to resolve (despite ‘hard’ reset - 60 seconds reset after power up) - realport is installed.

XCTU can find the unit (function Xbee Pro 900HP 10k, Port Com2 115226/8/N/1/N - API1, and thr MAC address)

Problem is - I can’t read the AT values of the xbee module - clicking on ‘read’ opens the ‘reading modules’ dialogue then I get an ‘action required’ window asking me to reset the radio module. I’ve tried resetting the connectport but I don’t think that is the problem (I think it’s the radio module)?

I’ve switched to another X2 unit - uninstalled the original realport and installed a new one. Same situation - xctu can see the unit (and I can access the web server ok on both of these) but I can’t read the radio values.

When these units first arrived xctu worked fine so it must be something I have done?

XCTU works fine with my RF modems so there doesn’t seem to be a problem there.

Can anyone point me in the right direction here? Thanks in advance

I’m on Windows 7 pro 64. XCTU is 6.3.1

The connect port X2 is not intended to be read by XCTU. You use its web UI for reading and modifying the radios settings.

Understood - but if Realport can’t connect to the radio (which you would think should allow a transparent connection to the radio and therefor alloow XCTU to see the radio just as if it were on a serial port) - how does one ‘get the data into the radio’ for transmission?

Thanks
Peter

Bumping this.

How are we supposed to configure Channel Mask and other settings without XCTU?

The CM command is a bitmask. You would need to convert the desired bitmask into a Hex value. You can do that using your computers Calculator.

That’s definitely not true about XCTU. I’ve used it hundreds of times to configure the ConnectPort X2D to pair them with an XBEE 900HP RF.

It’s worked great for years, but I’m starting to see the issue mentioned in the original post. XCTU will recognize the ConnectPort, but it appears to read the serial info incorrectly. I use the webpage to load a configuration file to set the baud to 19.2/8/1/Hardware, but XCTU will show Port Com2 115226/8/N/1/N - API1 and won’t read the AT values. That baud rate is incorrect, and it should be AT mode, not API1 mode.

Is there another way I can write AT values without XCTU? The webpage doesn’t have options to set those things. For starters, I need to set value AP (API Enable) to Transparent Mode.

You would need to go to the Web interface of the X2. Then under the XBee function, there is a option for direct access. That function would need to be enabled.

I have the same problem, I can’t access the AT parameters through XCTU to enable the api. Has anyone managed to solve this problem and could help me?

The XBee must already be in API mode for the X2 to be able to talk to it. If it is not in API mode, then you will need to use a remote radio connected as a Router and in API mode. Then you can use over the air commands to enable API mode.