I have just downloaded the new beta firmware.
I was previously using the 3.5.3-rc1.
I am using the Pixhawk 2.1 (The Cube), with the px4flow + lidarlite v3. These 2 items are connected via a i2c hub.
Lidarlite works fine.
The px4flow did not work well with the previous version. I would get no readings.
I used a hack, which was to boot the board via usb. Then plugging in the battery. This would give readings.
I have just tested the firmware in this thread and there is no difference. The issue still exists.
I am just wondering if there is a parameter which could be added, to add a delay to the boot-up of the board.
So, when the battery is inserted, the copter (including the px4flow) will power up. However, we wait x milliseconds, before the flight controller actually boots up. The value of x, should be changeable in the parameter configuration.
Another method might be to create a setting which allows us (via Mission Planner), to soft reboot the flight controller. So, when the battery is connected, the FC will bootup, though the px4flow does not work, so we press a button in Mission Planner, which soft reboots the FC, without disconnecting/reconnecting the battery. This may resolve the issue.
Both solutions would be subject to testing, which I can do for you, if you'd like. It'll take me less than 5 minutes to run the test.
I'd love to hear back from the developers regarding this.