Starling 2 Max doesn't report battery information
-
Hello,
I have a stock Starling 2 Max that has issues reporting data from the battery. I first tried adding the battery0, InstantPower value display in QGC, but it started at about 6W before I took off and never changed. The other values in that display, like altitude, did change correctly. I tried reading out voxl-inspect-battery but just saw N/A for all of the fields. I verified that voxl-mavlink-server, voxl-px4, and voxl-vision-hub were all running. My esc-tools version is 1.9 and the 4 in 1 ESC is board version 44, firmware version 39.21, and bootloader version 184. The system image is version 1.8.04-M0054-14, voxl-suite is version 1.5.0.
When I run px4-listener battery_status , it says "never published". During later testing, the battery display disappeared from QGC, so now I can't even see what the voltage on the battery is. I think this may be a hardware issue with either the ESC or VOXL 2. What do you think?
@Hunter-Scott Can you supply a px4 log file?
-
Here's the log: https://drive.google.com/file/d/1stxCxb1RBT4D_bQQzXKSdCcVKUDtqdxl/view?usp=sharing
I tried swapping in a Power Module board to read the battery data that way, but still saw that the battery_status was never published.
-
Here's the log: https://drive.google.com/file/d/1stxCxb1RBT4D_bQQzXKSdCcVKUDtqdxl/view?usp=sharing
I tried swapping in a Power Module board to read the battery data that way, but still saw that the battery_status was never published.
@Hunter-Scott The log you provided contained battery_status
-
@Hunter-Scott The log you provided contained battery_status
@Eric-Katzfey My mistake, I must have uploaded the wrong one. I went to capture another one today and I'm not seeing any log file get created after I fly. I verified that the px4-logger was running and ran px4-logger stop before removing power from the drone. I'm still unable to see any battery information and running px4-listener battery_status still says "never published".
-
@Eric-Katzfey My mistake, I must have uploaded the wrong one. I went to capture another one today and I'm not seeing any log file get created after I fly. I verified that the px4-logger was running and ran px4-logger stop before removing power from the drone. I'm still unable to see any battery information and running px4-listener battery_status still says "never published".
@Hunter-Scott If you delete all logs then fly you don't see any log files afterwards?
-
@Hunter-Scott If you delete all logs then fly you don't see any log files afterwards?
@Eric-Katzfey
I removed everything in the log folder, restarted, and did a quick arm and disarm and then a quick ~5 second flight. The logs that appeared are attached.https://drive.google.com/file/d/1B0klF8j9lnhJ8deYBedRbsjGmnCPjbYB/view?usp=sharing
https://drive.google.com/file/d/1qg1ukwoDxpKHZ7N6xCbN8W_yhpx_aDDN/view?usp=sharing -
@Eric-Katzfey
I removed everything in the log folder, restarted, and did a quick arm and disarm and then a quick ~5 second flight. The logs that appeared are attached.https://drive.google.com/file/d/1B0klF8j9lnhJ8deYBedRbsjGmnCPjbYB/view?usp=sharing
https://drive.google.com/file/d/1qg1ukwoDxpKHZ7N6xCbN8W_yhpx_aDDN/view?usp=sharing@Hunter-Scott When you swapped in the power module board did you update the px4 configuration file in /etc/modalai/voxl-px4.conf? In that file, how is POWER_MODULE set? For the power module it should be
POWER_MANAGER=VOXLPM. For standard Starling 2 Max configuration it should be NONE. Can you stop voxl-px4 running as a servicesystemctl stop voxl-px4, wait a few seconds, then run voxl-px4 from the command line in non-daemon mode withvoxl-px4 -dand let the startup script run through. At the command prompt typever allandqshell voxl_esc statusand then include all of the output here? In the log that you sent that did have battery_status, where did that come from? A different drone? -
@Hunter-Scott When you swapped in the power module board did you update the px4 configuration file in /etc/modalai/voxl-px4.conf? In that file, how is POWER_MODULE set? For the power module it should be
POWER_MANAGER=VOXLPM. For standard Starling 2 Max configuration it should be NONE. Can you stop voxl-px4 running as a servicesystemctl stop voxl-px4, wait a few seconds, then run voxl-px4 from the command line in non-daemon mode withvoxl-px4 -dand let the startup script run through. At the command prompt typever allandqshell voxl_esc statusand then include all of the output here? In the log that you sent that did have battery_status, where did that come from? A different drone?@Eric-Katzfey When I swapped in the power module board, I did not update voxl-px4.conf. I tried changing POWER_MANAGER to VOXLPM and rebooted but still did not see anything publishing on px4-listener battery status. I set it back to NONE (since I think the ESC should still be able to read power data because I have battery->power module board->ESC input). Below is the output of the commands you requested. The log that had battery_status did come from this same drone. It had been working, but then stopped, and I'm pretty sure I didn't change anything. Could the VOXL 2 have a hardware issue?
Command outputs:
https://pastebin.com/4FCVT6Vw -
@Eric-Katzfey When I swapped in the power module board, I did not update voxl-px4.conf. I tried changing POWER_MANAGER to VOXLPM and rebooted but still did not see anything publishing on px4-listener battery status. I set it back to NONE (since I think the ESC should still be able to read power data because I have battery->power module board->ESC input). Below is the output of the commands you requested. The log that had battery_status did come from this same drone. It had been working, but then stopped, and I'm pretty sure I didn't change anything. Could the VOXL 2 have a hardware issue?
Command outputs:
https://pastebin.com/4FCVT6Vw@Hunter-Scott Can you update to SDK 1.6.0? Then do the
ver allandqshell voxl_esc statuscommands again and attach the output? -
@Hunter-Scott Can you update to SDK 1.6.0? Then do the
ver allandqshell voxl_esc statuscommands again and attach the output?@Eric-Katzfey I updated to SDK 1.6.0, which fixed the power display issue. I was still getting no valid local position preflight fail, but after I ran apt update && apt upgrade, things seemed to work.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login