Ok, further info on the f9p board shenanigans. Got 3 brand new XBee’s. They came with carrier boards. Testing them each on a carrier board, they all came up fine and do what they’re designed to do. Now, put 2 of them on the x9p boards. Both work fine plugging in to the gps side and running u-center. However, plugging in to the XBee side, one appears to work just fine, the other not so much, on neither of the desktops (Linux and Windows) — they can’t see it the XBee. Swapped XBee units around, got the same result. That f9p gps board has stopped communicating on the XBee side.
I got 3 so I can have 1 base, 1 rover, and 1 to watch those two.
Make sure that the u-blox ZED-F9P UART2 is not outputting anything. This UART2 is connected to the XBee and it will not let you communicate from XCTU until you disable UART2.
I also would like to ask you to use a more suitable subject for the question. Other people will not be able to find this thread with this subject.
Neither f9p board had problems when they first arrived, and one of the boards (rover) still has no problem with the xbee connections.
Re: subject; that’s the best topic I could think of at the moment and since this board does NOT allow editing of anything after submit, can’t change it it seems.
Hi skypuppy, did you solve it?