Ok, thank you
Ok, thank you
Steri, I have been using Zubax GNSS since the first production and have always been impressed with the gps accuracies but have been equally unimpressed with the compass. I’m hopeful that the 3100 will be the answer.
I am using Zubaxx compasses right now and i must say that since i unloaded the other compass drivers and loaded only the UAVCAN, compasses work much better and don’t give us any more probs.
I’ll test the 3100 in the near future but i really don’t like I2C bus much.
Hopefully someone will come out with a UAVCAN F9P GPS with 3100 compass, that would probably be a really great combo.
Its been a while since you started testing the 3100. I just purchased one and its on its way. How did your testing go and are you still using it?
Has anyone tested yet? Any noticeable performance difference? Maybe in combination with F9P?
How much work do you think it’d be to back port the RM3100 driver to 3.6? Did the internal APIs change much between 3.6 and 4.0? I’d like to use the DroTek F9P Sirius RTK GPS, but I’m reticent to jump to 4.0 alpha for an expensive copter.
We merged the support into master, it should appear soon in next 4.0 RC too.
About backporting, it should be pretty simple as the library is really simple
Good day, ive purchase the drotek rm3100… as only on my gps I’ve an extra i2c port how i can configure it on MP?
My gps is wired on can node but ive saw that on the bottom of the can board I’ve also the spi pads… better i2c or spi?
Hoping for your advice…
what can node are you using? The ones I have seen have both a serial/i2c and a separate i2c.? As for the i2c vs. the spi I don’t have a lot of knowledge but would assume that spi if you have the connection and ability would be better seems as i2c is prone to errors.
ArduPilot probes the I2c bus for the 3100. You can run multiple devices in parallel on the i2c bus by using an i2c splitter or you can use one of the gps serial ports and connect only power, ground and SCL/SDA. The 3100 would not be available through the CANbus gps.
Good day, i have the mro can node… on the top of the board i have one I2C port and one 6pin pin serial port where ive attached the gps, on the bottom there are the pads but name of spi seems be different from the pinout scheme of the drotek spi pinout
Use the i2c port. Don’t worry about CAN, it’s of no use to you for the mag.
ok… but if i want use SPI what will be the difference coz i don’t like to much the i2c
I don’t think that spi will work. I2c is really not a problem with the 3100 as it cam be mounted much closer to the AP without issues. I have all of mine mounted less than 2cm from the autopilot with great results.
Sounds good that i2c don’t have any problem with this module… i will test it soon when it will arrive. Me I’ve already active two external compasses coz already on my gps board i need only calibrate and active the third external… correct?
How’s the results during the flight?
Yes you will have to select the primary compass and calibrate. I would choose the 3100 as primary as it will be much more accurate and less prone to interference. I have the 3100 on 3 vehicles and each is very stable with no compass issues at all, much better than any compass i have used.
My gps is connected on a can node and LIS3MDL and IST8310 soldered on gps board will be automatically recognized as compass 1 and 2… the 3rd internal and external are disabled by me due too high offset
Mag numbers are allocated by the firmware but you can select “primary compass” in mission planner to either 1, 2, or 3.
You are right i forgot there is a scroll menu option for choose use primary compass…
Thank you for your help and time
Good day, finally the module arrived… ive installed it… after the calibration the parameters after the calibration is really good…