setting up xbee

Q&A forumCategory: Questionssetting up xbee
skypuppy asked 3 weeks ago

I’m new to xbee, so please be gentle.  Hardware: two brand new ardusimple zed-f9p’s, 2 brand new xbee boards with 900 mhz comms.  One f9p, of course, will be base and the other the rover.  Apparently, makes no difference which is which.  1) Base has to have itself defined in which config table?  2) Rover has to have itself defined in which config table?
The xbee’s are mounted on your f9p standard mount points.  3) Is there software in ucenter, or where, to configure them for the f9p?
4) if the base has ntrip access (absolute), how do we get that data to the rover via the xbee comms?
5) If the base does not have ntrip access (relative), how do we get that data to the rover via the xbee comms?
6) Does the rover care if the base has ntrip data?  That is, do we need to configure anything differently on the rover?
Thanks.

6 Answers
Ardusimple Staff answered 3 weeks ago

Hi skypuppy,
1) Base has to have itself defined in which config table?
Base station is sent pre-configured (see https://www.ardusimple.com/question/example-configuration/ for configuration details)
2) Rover has to have itself defined in which config table?
Rover is sent pre-configured (see https://www.ardusimple.com/question/example-configuration/ for configuration details)
3) The xbee’s are mounted on your f9p standard mount points. Is there software in ucenter, or where, to configure them for the f9p?
All XBee modules are sent pre-configured. You can change their configuration via XCTU software from Digi by conencting your PC to the simpleRTK2B board via POWER+XBEE connector.
If you are not an expert in XBee radios, we don’t recommend to play with their configuration and if you do, please do a backup of the original configuration.
4) if the base has ntrip access (absolute), how do we get that data to the rover via the xbee comms?
The NTRIP absolute precision is automatically sent to the rover via the RTCM messages from the base station.
5) If the base does not have ntrip access (relative), how do we get that data to the rover via the xbee comms?
The relative data is automatically sent to the rover via the RTCM messages from the base station (if you enable/disable NTRIP corrections, you will get absolute accuracy or not on the rover).
6) Does the rover care if the base has ntrip data?  That is, do we need to configure anything differently on the rover?
The configuration in the rover is the same so it doesn’t really care.
The only difference will be in the accuracy of its position, while the precision wrt the base station will remain the same.
Best regards,
ArduSimple Team

skypuppy answered 3 weeks ago

Thank you MUCHLY!

skypuppy answered 3 weeks ago

I am confused about one (new) part.  Downloaded the base and rover firmware.  So, how do I load these?  Install them are normal 1.10 firmware, with no boxes checked, just like the regular firmware update?  Or do these files contain only parts that are just config parts and if so, how do I write them to the Ardusimple f9p boards?  And we load that via the usb port on the same side as the antenna connector?

skypuppy answered 3 weeks ago

Only base/rover configs downloaded to the PC that is, not the f9p’s.

Ardusimple Staff replied 3 weeks ago

Configuration files and firmware are two different things, each one is uploaded in a different way.
For the configuration files, you need to do it via Tools > GNSS Configuration …, select the file and File > GNSS.
You can brick your board if the firmware of the config file does not match the one in your board, so double check it before proceeding and ask any doubt you may have.

skypuppy answered 3 weeks ago

uh-oh.  I loaded it via the method for the firmware.  f9p still seems to working, though.  This is the filename I downloaded from your place (I think) :  srtk2b_base_FW_HPG110.zip.  It’s that “FW” in the middle that made me think it was FirmWare.

root Staff replied 3 weeks ago

The configuration files are different for each firmware version.
To avoid problems we suggest that you return to the default configuration (UBX>CFG>CFG) and load the configuration file properly.