Yes I am using the antenna’s from the digi mesh kit and they are connected to the modules on the Grove board the kit comes with. The physical distance apart on these are handful of inches to a foot in front of me on my work bench next to my PC. The coordinator is connected to the PC with your micoUSB to USB cable. The Router is powered with a rechargable 1000 ma Lithium battery pack thru the 2 pin PH connector on the Grove board. This is the physical setup when I start-up the modules hence running the micopython code I flashed into them. Yes I am using the ZigBee manuals.
Here’s a clearer picture how I do things.
I use XCTU to do all configuration settings and it’s internal MicroPython terminal to flash the code into a module (at the >>> I import os and then os.format() before every micropython code flash of ctrl f followed by ctrl d). I only have one module at a time connected to XCTU thru the microUSB to USB cable to the PC when I do settings and flash a module. From here I connect things as I described above. First I connect the Coordinator to the PC via the cable (network discovery time is 0xFE, 254 seconds, so I have plenty of time to power up the Router with the Lithium battery) then I run and setup TeraTerm (or the serial console in XCTU optionally) so a terminal is ready when I plug the battery into the grove Router board to view the data the coordinator received from the router. I can also use the reset button on the router too if within the network discovery time.
Where in my micropython code for the router and/or coordinator or both would you like me to put the AT command NR0 to be executed?
Notes: The ‘AI’ = 0x21 I see on the router is when after I powered down the setup and connect the router to XCTU and look at the configuration settings is where I saw that. I think that got set because powering down is literally unplug the modules hence losing power and I usual unplug the coordinator first I noticed of myself.
The coordinator can be flashed with any FW version (1006,1007,1008,100A,100B,100D for example) and if the router is flashed only with a working FW version (1006,1007 or 1008) the code runs as expected ie ‘Hello World’ 3 times and then streaming ‘10.0’. If the router is flashed with a FW version not 1006, 1007 or 1008, the code only does ‘Hello World’ the one time with any FW versions that are in the Coordinator.
I noticed the paste above in my original post that appropriate indentations in the micropython code are not there. I can assure they are in the actual code.
Do you have any code you can share that I can program the coordinator and router with that runs in transparent mode similar to mine that is known to work with FW versions 100D and higher. The XB3-24 modules that can be purchased nowadays can only use FW version 100D and higher. I did purchase a new digi Mesh kit that has the newer modules and they came with FW 100D. I also programmed them with my code and the code only executes one ‘Hello World’ just like my older digi Mesh kit. Also I have been to and am aware of digidotcom website for code snippets as a resource and within the ZigBee manuals and actually my code uses some of them.
My large project actually is more suited to run in transparent mode as it’s more like a laboratory setup that I need to stream live near real time data from 6 to 10 independent sensors into one coordinator each at a rate of about 4 samples per second and get that data into a PC for analysis by a custom program I wrote in Python and QT. This code I flash into the xbee3zigbee3 modules is much more complex than the test code and it works fine as long as the FW versions are 1006,1007,1008. But new modules that will be used can only be FW versions 100D and higher and my actual code does not run. I narrowed down the problem to the test code I pasted; seems transmit() works only once and on the first encounter and won’t allow another or following transmit() successfully.
I actually have built custom PCB with modules and other electronics components on them and been running my large project successfully for months. I recently upgraded the FW and at the same time noticed new modules only work with FW 100D and higher and for me out of the blue this problem happened. I really have put many hours into finding the problem that I can’t solve before posting here.
Again I honestly thank you for helping and hope you will continue to help.