@daniellee This log shows a normal flight happening in altitude hold mode. RC inputs are coming in and motors are spinning. Was there some issue with the flight this log was captured from?

@Jetson-Nano Can you rebuild to add UAVCAN? The code is here: https://github.com/modalai/px4-firmware/tree/v1.14.0-2.0.133-dev

@RoyAzriel I would just grab the most recent one.

@Mustafa_Cayci You can get the Starling 2 Max with a ToF sensor for depth mapping indoors (The sensors don't really work outdoors). https://www.modalai.com/products/starling-2-max?variant=49129974923568

@gerard I also just remembered we had a stint of bad MCBL-00010's a few months ago...
We have since cleared that up, but there is no telling how long ago you may have ordered that cable...
Please see this thread for guidance and if you do think your MCBL-00010 is at fault, we will replace your M0048, just reference both threads in your RMA (this one and this one -->) https://forum.modalai.com/topic/4632/flight-core-2-firmware-update-through-qgc?_=1781284416780

Hi @Jetson-Nano,

Can you please clarify the following - in your original post, you mentioned that the third party ESC also had issues, however in the post above you said no issues. I am quoting your notes from above:

"
Scenario 3 – Third-Party ESC Evaluation
To further isolate the issue, we replaced the VOXL FPV ESC with a NeutronRC X-CLASS 4IN1 ESC V2 (3–8S, 70A) configured using the DShot protocol.

During testing, we observed the following:

ESC temperature increased rapidly, reaching approximately 80°C to 90°C within two minutes of flight.
One motor would subsequently stop during flight.
The aircraft would lose stability and crash.
"

I just wanted to clarify what actually happened and then we can investigate further. Than, you for providing the diagram, i think it looks OK.

I have never seen this behavior where the ESC reports incorrect voltage and these short spikes in temperature. This may point to a hardware issue on the ESC board, but i do not actually know where it might be or what would cause it. Have you visually inspected the FPV ESC that has this issue to see if any components appear damaged or anything looks unusual?

Alex

@Eric-Katzfey We are experiencing connection issues between VOXL2 and QGC.

QGroundControl is showing disconnected after inputting the comms link with 192.168.7.2:14550 in UDP. mavlink_to_gcs and mavlink_from_gcs are both reporting data. voxl-px4 and voxl-mavlink-server are running.

voxl-my-ip
192.168.7.2 (usb0)

@astro_phil , OK, thanks for testing. I will check it myself tomorrow.

Alex

@LukeNow This worked, thanks.

@JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

@voxltester Use any port you like. When you connect to voxl-mavlink-server at port 14550 it will remember the ip and port you connected from and maintain a connection with it.

@PatkirkMartin No, as I said a UART mapped to the applications processor would also work. PX4 has a split architecture on VOXL2 with all flight critical operations happening on the DSP and support functions such as Mavlink, logging, and data manager are on the applications processor. But there is flexibility to move functions between them as needed. So, to match the ELRS receiver with the Mavlink module you could run it on the applications processor instead of the DSP. However, you would need an expansion board that exposes such a connector.

@ApoorvThapliyal : the problem (Error message: "set_position_target_local_ned: coordinate frame 0 unsupported") appeared in QGC after updating VOXL SDK from 1.5.0 to 1.6.3.
The error blocked me from being able to use QGC to calibrate or arm the drone. Stopping and restarting voxl-vision-hub solved the problem.
For now I'm using voxl-vision-hub as it comes on SDK 1.6.3 (no changes yet) and have not made changes to the .conf file (yet).

@vmbasvi That appears to be a Microhard modem, not a WiFi dongle.

@Ben-Linne : Thanks for the excellent instructions. Worked perfectly first shot. betaFPV is back to normal and binds to the radio controller ! Best regards, Hector

@jon When running that way make sure you wait a few seconds before restarting. If you ctrl-c out of voxl-px4 and immediately restart voxl-px4 you will see that error condition.

@Eric-Katzfey UAVCAN is working in the latest versions, when enabled. And yes I meant heading error, thats my mistake.
The collision prevention is the major issue I am having.
The heading error is in the latest version, and I also came across it in the issues section and it was shown solved, but I did not test it out still with VIO, I was testing with only Optical flow and it was not working.

@Alex-Kushleyev

Thank you. We will do, but for future reference:

@Alex-Kushleyev said in Burnt board components:

what type of vehicle was the ESC a part of?

Singer Vision FPV 3.5"

@Alex-Kushleyev said in Burnt board components:

what was the behavior of the motor that was not functioning properly?

Not operating a full power with intermittent operation

@Alex-Kushleyev said in Burnt board components:

did the whole ESC stop working or only one channel, which was originally struggling?

Only one channel

@Alex-Kushleyev said in Burnt board components:

did you notice the burned component when the ESC arrived or did it burn after arrival?

We didn't noticed or inspected it.

@Alex-Kushleyev said in Burnt board components:

was the black paint already on the ESC when you received it?

We didn't notice or checked

@Eric-Katzfey We reinstalled the QGC in a new laptop and it is working fine now.

@jameskuesel ,

I think there is another option which i have not considered before. The first three cameras are the same as above:

: M0173 J1: AR0144 slot 0 : CCI0 : M0173 J2: AR0144 slot 6 : CCI1 : M0173 J5: AR0144 slot 2 : CCI2

Then if we use J8U (which can be done using M0181 - it allows you to connect a Boson sensor to lower slot, and a tracking / hires camera to upper slot). Then the fourth camera would be:

VOXL2 J8: M0181 Upper : AR0144 slot 5 : CCI3

And there are no CCI conflicts.

One issue is that we don't typically sell M0181 by itself (only in a kit). Instead you could use two other options, both of which allow connecting a tracking / hires camera to the upper slot:

M0194 : https://www.modalai.com/products/m0194/ M0172: https://docs.modalai.com/M0172/ / https://www.modalai.com/products/mdk-m0172-1-00

The only down side of using M0172 / M0194 instead of M0181 is that the two alternatives do not have a mounting hole that would align with VOXL2 mounting hole, but M0181 does have a tab with a mounting hole for VOXL2 J8, see below. The M0172 and M0194 were really designed as mainly options for VOXL2 mini.

98d5f0ec-7f07-44bf-b002-036aefd3921d-image.png

c9c77086-b5fc-4215-99a2-fdc310d6f18c-image.png