Do you guys have a white paper or any documentation describing how your setup works with the simplertk? I’ve watched all the videos from your “main page” but there is overview of the xbee and how you’ve implemented it. Been plugging away at it for several days now, and while I can use xtcu on each computer to take to the xbee modules and have them do the built in tests successfully, I still don’t think they are talking to each other for the base to give the rover rtcm corrections. A 24 hour run with or without the base physically turned on gives the same readouts on location from the rover. In short, it’s not working as your company implies. There must be some setup I’m unaware of. PLEASE help!
The ArduSimple boards don’t add any magic or micro-controllers, so the underlying hardware functions as those devices would under any other context. A schematic might be helpful but the block level connectivity isn’t complex.
The ZED-F9P should be using UART2 at 38400 baud to send/receive the RTCM3 data unless other settings are reconfigured. The XBEE and ZED devices should be configured to use common rates, and the XBEE needs to transparently send all data received from one module to the next.
With zero margin hardware sales the support burden falls more on the end user/integrator, paid services are available for those needing additional assistance, whilst not increasing the costs to everyone else. https://www.ardusimple.com/store/
I would recommend connecting the the ZED USB to power/observe the device rather than the FTDI/XBEE USB
The Base needs to output the RTCM3 messages 1005, 1074, 1084, 1094, 1124 (or MSM7 equivalents), 1230 to UART2 at the baud rate expected by the XBEE. The ZED Base needs to complete a Survey In operation or be programmed with a static location for the 1005 message to be sent.
All our MR and LR kits come pre-configured to send/receive corrections as soon as they are powered.
Did you get the XBee radio modules from us as part of a kit?