I did a Part 107 job today at 0900. It all
fired up and I got what I needed in one
battery, but since my Notam was in force
until noon, I decied to shoot some additional
images for me. When I started the Spark
with the second battery, I got the firmware
update request, which i have been ignoring
because of obvious issues, and i have been
recieving the airport database update request,
which up until now has allowed me to bypass  
with an ignore option. But on the second start
up, I did not recieve the connected indication,
but it said "Cannot take off".

Can someone give some insight please?
If I don't have to update, I would rather
not, but if I am forced to, well, I am forced
to.

P.S. I have been looking hard at P4P+
to move up to a 1" sensor, but it looks
like I am back in the Mavic camp with
today's announcement. I read up on the
M2P's for a while before I order one.

Thanks!

I think that the battery version of this second battery is back level.

Charge the original battery and test with it and see if the FW incompatibility error clears.

Good point. I did add sixth battery  a
few weeks ago, which I updated when I
bought it & I was hoping  that this issue
was caused #6, but it wasn't. It was #5,
so I will try again today with the battery
that I flew with.

Thanks for the comment.
Edit to add: I am trying to equally cycle
through my batteries so I don't always
use the same ones. I have them numbered
in the order in which I bought them to help
me keep track of their ages & help me to
be aware of any issues with any particular
battery. But I really can''t say if I have flown
with #5 either, so it may not have been
properly updated. I'll try my 1, 2, & 3 batteries
today, as well.

It was the battery. Either I forgot to update
it, or it didn't update correctly.

Thanks!