RocketMouse's blog View Details
Posted by RocketMouse | Mar 30, 2019 @ 05:33 PM | 1,856 Views
if you look at the GPA.Delta messages you will see the time in milliseconds between parsed positions. This should always be around 200 milliseconds +/- 20 milliseconds. If you see jumps on the order of 400 milliseconds this indicates an error.

if it drops the DOP messages/HW debug messages, but those are not that important. The main one it will let you know is if you miss a PVT message, which is very important.

__________________________________________________ _____________

So I finally got this all hooked up and tested. ArduPilot checks for a location update every 20ms. So the GPA.Delta log shows that timing, and that is why it appears to be in 20ms intervals. These are on my test Solo sitting out on my deck using the brand new mRo M8N GPS. I had good reception and navigational use of all three systems.

The results confirm what I afraid of. I have not flown it to see if the results get event worse in flight, but they certainly may.
With the typical configuration of 2 systems enabled (GPS & Glonass), the location updates come in on time with a new location every 20ms or less, where you see them at 0 to 220. There are no errors, and everything is happy.

With the mRo configuration of 3 systems enabled (GPS, Glonass, & Galileo), location updates are consistently running late, and have quite a bit of jitter, where you see them spike up to 240. And there are numerous delayed updates in excess of the...Continue Reading
Posted by RocketMouse | Dec 10, 2018 @ 03:28 PM | 8,276 Views
PB1 and PA7
Softserial1 TX pin and Softserial2 TX



set pan_inverted=on

First calibration:

- First thing to do is properly set pan0 (stop pulse).
- Place the mag as far as possible of power wires and metal objects.
- Then calibrate the mag. If should spin counter clock wise during calibration. It it do it clock wise then your pan servo is reversed, and you should to mod it for counter clock wise spinning.

set mag_declination = xxyy
set offset_trim = 0
set offset=0
- Calibrate compass again.
- Try to fine tune pan0 and min_pan_speed
- Set PIDs values properly


Pan - PWM1
Tilt - PWM2
Home button to PWM5.
Select button to PWM6.
Display to I2C port
Bluetooth to UART1
Local GPS to UART2


1. Short bootloader pins (Boot headers (11) - check pdf from link above), connect Usb.
2. Using Betaflight or Cleanflight configurator in Chrome upload SPRACINGF3_**.hex FW from here


1. Download and install Configurator from here
2. Run Configurator from Chrome Apps. Select Com port, select Bauds 115200, press Connect. Press CLI ENTER. Now...Continue Reading
Posted by RocketMouse | Nov 06, 2018 @ 08:32 AM | 9,243 Views


no soft serial in AP yet...sorry

The F4 processors have a dedicated VCP port for USB, not like the previous generation boards which had a USB-serial chip feeding a UART on the uP.
The Omnibus F4 boards pins out only UART1, 3, and 6, however, UART3 pins are shared with I2C (for external compass/airspeed) on the port for AP, I2C is enabled and UART3 disabled. It is possible to change the HWDEF and recompile to disable I2C and use UART3.


Omnibus F4 Pro V3
OMNIBUS F4 schematic

2 UARTs since UART3 is always used for I2C in Ardupilot firmware
Sport support does not really exist yet
rssi solder pad to PIN 0 on omnibusf4pro, can be used for either ana rssi, ana arspd or any other analog voltage function desired.

PWM5 and 6 are pwm outputs, functions is set by SERVO5 and 6 function param

arducopter4.rar - Custom FW by Atx_Heli with Uart4 - SERIAL2


F405 Wing
UARTn = SERIALn except for USART2 being used for RCInput, so SERIAL2 stays empty
RSSI pin voltage is 0-3.3 v
the SD card reader is very picky (I had also trouble with logging) They stated that only 50% of...Continue Reading

QLrs faq + info

Posted by RocketMouse | Dec 09, 2017 @ 03:32 PM | 16,212 Views
Flashing tips

QLRS FW supports E32-TTL-1W and E32-TTL-100 HW + similar 868 modules

Maximum range of this LRS has not been tested yet. You are welcome to be the first who will find this out.
QLRS supposed to provide better range than any other LRS that uses FSK modulation such as OpenLRS, ULRS etc.

Telemetry data is transmitted from UAV to ground station only! There is no full duplex link and it's not expected.

QLRS does not support full mavlink. The mavlink data is "converted" to some internal protocol, sent to the ground, and then mavlink message is resumed there.
Thus, the following messages (correctly the fields) that FC sends to QLRS are interpreted.
Then the same message is generated on the ground and they reach the software that displays the map, etc. etc.

__________________________________________________ __________________________________________________

Why is this project not opensource?
Originally Posted by qczek
Sorry, but currently there is no any developer interested in development, so sharing code only to starts someones commercial kick starer is not what i want to do
When I decide to stop development and there will be some not fixed bugs, i will release source code, don't worry.
If you are interested in any particular piece of coding i can share it no problem...
__________________________________________________ _______...Continue Reading