I don’t know what is going on here, this board use to work without any problem. Should I consider this as a hardware issue or not? I tried to reset all registers back to default and flash the newest firmware to it. Nothing works.
This device wants 1A of current or more at 3V. The USB port is not capable of providing that. You must power this device with an external power source using the barrel connector.
The first sequence of four lines there is the hex representation of “AT+++\r” repeatedly. If you’re already in X-CTU but have the console interface open when it performs operations against the XBee you will see its own data both to and from the XBee.
Color is important, traffic to the XBee will be one color (blue I believe) and from will be another (red). That information is missing from your copied content so it’s harder to figure out what’s going on. I see that you had problems uploading a screenshot, can you restructure the hex data to indicate direction of traffic?
A shot in the dark is that the data after the AT sequence appears to be a set of repeating patterns. It’s certainly not command data. I can think of a couple possibilities to try to rule out:
Somehow you may have captured the X-CTU discovery port scan. The reason this seems possible is because the patterns have a structure that makes it look as if this could be a series of framing errors at various baud rates. Probably being done in a decreasing order because the substring patterns are getting longer, indicating that an increasing number of character frames are being thought to be received.
Are you using transparent mode? If so, this could be data being transmitted from an established connection.
Yes, the module is receiving that message, not sending those message. we did find a device are sending those message to this module after a firmware upgrading. The problem is on the other device not this one. Thank you for your help.