I can’t find anywhere how to use the X-CTU in API mode
can there be step by step for simple API command?
X-CTU modem configuration-> read , not working
any guide how to use it (got the x4 kit)
getting “failed to enter command mode
Unable to read Version (ATVR)
Read Paramters failed”
but in terminal ATVR return 2241 with out any problem
any summery of diffrent version, devices name XBee series 2, series 1,diffrent stacks
how to config them as router,cordinator,end devices?
how to use AT to turn on/off led 1/2 (led 3 is atd4)
the schem show they are connected to do8,dio9.
can it be done using AT?
Take special note of the “Assemble Packet” section of that manual. To know what to put in your API packet, you’ll need to refer to the Product Manual of whatever type of firmware you’re using. I see the firmware you’re using is ZB, and the link to that Product Manual is on this page:
See chapter 9 at that link, but additional information on API operation is found throughout the manual.
X-CTU modem configuration-> read , not working
any guide how to use it (got the x4 kit)
getting “failed to enter command mode
Unable to read Version (ATVR)
Read Paramters failed”
but in terminal ATVR return 2241 with out any problem
A) Version 2241 is an AT type firmware, so I suspect the “Enable API” box is checked on the PC Settings tab of XCTU. Uncheck this box to speak to modules with AT firmware loaded in them.
any summery of diffrent version, devices name XBee series 2, series 1, diffrent stacks
how to config them as router,cordinator,end devices?
A) That’s a very broad question, and the answer to that would be found in various articles and the Product Manuals throughout our website.
how to use AT to turn on/off led 1/2 (led 3 is atd4)
the schem show they are connected to do8,dio9.
can it be done using AT?
A) This answer would be found within the Product Manual of whichever rf protocol type is being used. Normally this information would be found in the section about AT commands.
XTCU user guide is not connecting between API and “Assemble Packet” in XTCU user guide, this is not clear as a beginner.
simply example with picture (like how AT is used) will be great.
so
a: checked “Enable API”
b: going terminal->assemble packet
c: write for example 7E 00 0F 17 01 00 13 a2 00 40 55 6c 7e FF FE 02 49 53 18
d: press send data
e: then? to wait?
f: close
am I right?
2)still not working, with unchecked “Enable API”
the XTCU point me to “get new version” and web download is returning “The connection with the server was reset”
ok
the product manual doesn’t say any thing about the usb dev board. couldn’t understand how it is expected to know which ATD? is connected to led 1/2/3/4
maybe from the schematic?
I have found the same difficulty with Digi’s documents. Most are very unclear and the information is either missing or scattered throughout many documents and within the example Python scripts (but without adequate comments).
The schematic for the XBIB-USB dev board does not completely match the switch and LED reference designators so some guessing and experimenting is required.
Some hints that may help. Look up the AT commands D0, D1, D2, etc and P0, P1, P2 in the Xbee radio module document (90000976) for configuring an setting the DIO/A lines. The AT command ‘IS’ for reading the DIO/A lines .
In X-CTU read the ‘modem’ configuration and look for the DIO/AI pin configuration (the LEDs with be set as outputs).
As the previous post noted your module has firmware 2241 which is an AT router. This module DOES NOT support API commands. The Xbee Doc (90000976) makes it seem that all of these firmware versions does support API commands but this is not true. Look in section 10 for a list of AT commands and then read between the lines elsewhere in the doc with the AT/API commands. Check pages 40, 74, 79-82.
Also be aware that they mix AT commands into an API frame. I find this to be very, very confusing. If the doc shows an API frame structure then the information DOES NOT APPLY to 0x2241 firmware (see page 135).
So back to X-CTU. Leave the API box unchecked. In the Terminal tab type the ‘+++’ to go the command mode and ‘ATD44’ to set DIO4 low or ‘ATD45’ to set the DIO4 line high (I believe that one of the LEDs is connected to DIO4). Just remember that the ‘+++’ will timeout in a few seconds.
Don’t feel too bad as it has taken me several weeks to figure this out from Digi’s documents, reading this forum (good idea to go through and read every thread here) and experimenting with the hardware/software.
just to be clear
if I want to config for example sleep time of 0x2241
I can’t do it from other device as API is not supported
only from connected PC device using the AT
The sleep time can be set from the coordinator but I have not dug into the details of this. I set-up my PAN through the Digi Dia which does take care of all the details.
My coordinator is running firmware 0x2141 which is an API coordinator connected to a Wi-9P board. The Digi Dia does all the command translations and knows how to send the sleep set-up commands to a remote node.
This is correct. In order to configure remote parameters for 0x2241, you’d need to do this from an API device such as a ConnectPort X, or a module using an API-enabled firmware. If such an API device doesn’t exist, you’d need to configure the sleep settings on 0x2241 directly using AT commands.
A tip: save writing the SM parameter for last. Since that sets the sleep mode, once the module has begun its cyclic sleep schedule it can be difficult doing any further configuration.